Phenomenon of a node set as management (disk mode) being assigned as the master node of a queue during cluster configuration #11349
-
Describe the bugI have configured a cluster with rabbitmq node1 (disk mode), node2 (ram mode), and node3 (ram mode), and used ha-mode for a specific queue. At this point, I added the setting "queue-master-locator":"min-masters" to allow the queue's master to be set. Ultimately, I discovered a phenomenon where node1 (disk mode) is set as the master node of the queue. Here, I'm curious about two things: In a clustering environment, if the ha-mode master of the queue is selected as node1 in disk mode, will there be any performance issues? I'm looking forward to your assistance. Reproduction steps
Expected behaviorIn a cluster environment using ha-mode, the management node operating in disk mode should be excluded from selection as the master node of the queue ha-mode. Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
There is no such thing as a "management node" in RabbitMQ since 3.6.7 (shipped in 2016 or 2017 IIRC). All nodes collect their own stats, and all nodes that have the management plugin enabled can serve HTTP API requests. The recommended monitoring option is Prometheus and Grafana, or an alternative set of tools that use the Prometheus format. Mirrored classic queues will be removed completely for RabbitMQ 4.0, in fact, the a pull request to remove them is close to being ready. Their doc guide has been flashing very visible warnings for years now). So will be RAM nodes are they are completely incompatible with Khepri. See quorum queues (have been around since 2017-2018) and streams (have been around since 2021). |
Beta Was this translation helpful? Give feedback.
There is no such thing as a "management node" in RabbitMQ since 3.6.7 (shipped in 2016 or 2017 IIRC). All nodes collect their own stats, and all nodes that have the management plugin enabled can serve HTTP API requests. The recommended monitoring option is Prometheus and Grafana, or an alternative set of tools that use the Prometheus format.
Mirrored classic queues will be removed completely for RabbitMQ 4.0, in fact, the a pull request to remove them is close to being ready. Their doc guide has been flashing very visible warnings for years now). So will be RAM nodes are they are completely incompatible with Khepri.
See quorum queues (have been around since 2017-2018) and streams (have be…