When a queue cluster node's disk failed, the node was removed from the cluster. After restarting another node, a small portion of the metadata in the cluster was lost. What could be the reason for this? #12343
-
Community Support Policy
RabbitMQ version usedOlder (out of support without a commercial license) How is RabbitMQ deployed?Debian package Steps to reproduce the behavior in questionWhen a queue cluster node's disk failed, the node was removed from the cluster. After restarting another node, a small portion of the metadata in the cluster was lost. What could be the reason for this? |
Beta Was this translation helpful? Give feedback.
Answered by
michaelklishin
Sep 19, 2024
Replies: 1 comment
-
|
RabbitMQ 3.11 is completely out of support. Exclusive and non-replicated queues residing on the removed node will be removed together with the node. That's the definition of "non-replicated". |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
michaelklishin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RabbitMQ 3.11 is completely out of support.
Exclusive and non-replicated queues residing on the removed node will be removed together with the node. That's the definition of "non-replicated".