Replies: 2 comments
-
|
RabbitMQ 3.13 has been out of community support for well over a year now. According to the logs, a quorum queue Raft cluster fails to start a replica because a process it attempts to start is already running. There is only one place in our Raft implementation where that specific message is logged, and it does not have an It would be trivial to add but 3.13 won't get any more public releases and 4.1 will follow suite in Jan 2026. So the only way out for you for now is to reduce the churn of quorum queues (which is required to reproduce per your own words) and then upgrade to, say, |
Beta Was this translation helpful? Give feedback.
-
|
@PhBouzid can you share the rest of your logs? Specifically we need to clarify if this message can be present in the logs: rabbitmq-server/deps/rabbit/src/rabbit_quorum_queue.erl Lines 932 to 935 in b909a81 That would mean that a part of queue state related to its Raft member failed to be deleted. Quorum queues were not designed for churn and in every scenario we could think of there's only so much a QQ can do to protect itself (or its future incarnations) from churn. But some team members want to reconstruct the sequence of events. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
First of all, I would like to thank you for your work on RabbitMQ. It has been a reliable and fundamental component of our system for many years.
Community Support Policy
RabbitMQ version used
3.13.6
4.1.x (we faced an issue with shovel recreationl)
Erlang version used
26.2.x
Operating system (distribution) used
Kubernetes
How is RabbitMQ deployed?
Community Docker image
rabbitmq-diagnostics status output
See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics
Logs from node 1 (with sensitive values edited out)
See https://www.rabbitmq.com/docs/logging to learn how to collect logs
Logs from node 2 (if applicable, with sensitive values edited out)
See https://www.rabbitmq.com/docs/logging to learn how to collect logs
Logs from node 3 (if applicable, with sensitive values edited out)
See https://www.rabbitmq.com/docs/logging to learn how to collect logs
rabbitmq.conf
See https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location
Steps to deploy RabbitMQ cluster
We deploy RabbitMQ using Helm.
Steps to reproduce the behavior in question
Create vhost
Create quorum queue
Create shovel between queues
Use the system normally (publish/consume messages)
Delete:
Shovel
Quorum queue
Vhost
Recreate all of the above with the same names
Repeat steps 1–6 multiple times
advanced.config
See https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location
Application code
# PASTE CODE HERE, BETWEEN BACKTICKSKubernetes deployment file
What problem are you trying to solve?
We are running RabbitMQ 3.13.6 and are observing an issue where quorum queues become impossible to re-declare after multiple recreate cycles involving shovels and queues. At some point, the quorum queue enters an inconsistent state and cannot be created again, even though it was deleted via API.
We would like to ask:
Is this a known issue in RabbitMQ 3.13.6?
Could upgrading to RabbitMQ 4.1.5 potentially fix this behavior?
Or are we performing the recreate process incorrectly?
Process Description
In our system, we dynamically manage infrastructure and regularly recreate both quorum queues and shovels.
Our typical workflow:
Create vhost
Create quorum queue
Create shovel between queues
Use the system normally (publish/consume messages)
Delete:
Shovel
Quorum queue
Vhost
Repeat the same process again with the same names
This recreate cycle can be executed many times automatically.
After several iterations, quorum queues stop being recreated correctly and start failing during startup or declaration.
I found that there was the similar issue without answer:
rabbitmq/ra#410
#13827
Beta Was this translation helpful? Give feedback.
All reactions