Quorum queue not remove member that not exist anymore on cluster. #11213
Unanswered
leomartinslima
asked this question in
Q&A
Replies: 2 comments 4 replies
-
I think @SimonUnge can you submit the docs for this feature? Thanks |
Beta Was this translation helpful? Give feedback.
4 replies
-
Yes, let me add a section in the QQ chapter! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a RabbitMQ cluster with three nodes, using quorum queues distributed among the three nodes. This cluster is set up to utilize an auto-scaling group. When an EC2 instance dies and another instance joins the RabbitMQ cluster, the quorum queues, where the node that died was the leader, still reference it as if it remained active.
In the queue details, we see three nodes online, but in the members section, there are four nodes listed.
The problem occurs with the quorum queues when another node, which was a pair of the node that died, also fails.
I have tried removing this reference using the following commands:
rabbitmq-queues shrink
rabbitmq-queues delete_member
I also tried running some commands from the other nodes like:
rabbitmq-queues grow rabbit@hostname all
rabbitmq-queues rebalance quorum
However, these attempts have not resolved the issue.
In conf the rabbitmq is set
cluster_partition_handling = autoheal
cluster_formation.peer_discovery_backend = aws
cluster_formation.aws.region = ${AWSRegion}
cluster_formation.aws.use_autoscaling_group = true
cluster_formation.node_cleanup.only_log_warning = false
cluster_formation.discovery_retry_limit = 20
cluster_formation.discovery_retry_interval = 2000
RabbitMQ 3.13.1Erlang 26.2.3
If anyone can help me
Beta Was this translation helpful? Give feedback.
All reactions