Deprecation of queue-master-locator for 3.9 and newer

Bug #2091140 reported by Roy Zuo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack RabbitMQ Server Charm
In Progress
Undecided
Unassigned

Bug Description

queue-master-locator option is deprecated and replaced by queue-leader-locator, which accepts different values.

https://github.com/rabbitmq/rabbitmq-server/issues/10702

According to this, if queue-master-locator is still used, "random" and "min-masters" will be mapped to "balanced" of queue-leader-locator.

https://www.rabbitmq.com/docs/clustering#replica-placement

However, in production, we find that the queue-master-locator option is not always correctly mapped, which can cause a node to abruptly terminate itself and subsequently lead to cluster partitioning.

```
Nov 13 15:09:11 juju-d66aa4-2-lxd-16 systemd[1]: rabbitmq-server.service: Control process exited, code=exited, status=78/CONFIG
Nov 13 15:09:17 juju-d66aa4-2-lxd-16 systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'.
```

The above is observed with RabbitMQ 3.9.13 on Ubuntu Jammy.

Since the queue-leader-locator defaults to "balanced", which is overall a good default, there is no point in rendering the queue-master-locator for versions 3.9 and newer.

Also, the output of the `rabbitmqctl environment` command for versions 3.9 and newer will not show the "queue-master-locator" output by default.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-rabbitmq-server (master)
Changed in charm-rabbitmq-server:
status: New → In Progress
Roy Zuo (roylez)
tags: added: sts
tags: added: customer
tags: removed: customer sts
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.