-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blocked channels and queues using HA #581
Comments
FTR, this was discovered in an escalation and the investigation is still in progress. We have a patch candidate but it needs testing. We also have a couple of potentially related issues which we haven't gotten to the bottom yet, which may or may not be actually related. |
Here the steps to reproduce the issue: 1 - RabbitMQ cluster with 3 nodes
Setup this policy:
2 - Execute the following script to one node, ex:
3 - execute this python or/and this java scripts 4 - after a few minutes you will see the command On the management UI you will see channels with unknown connection |
To make it clear: this issue is about (one more) missing/unreasonable timeout value. There can be more issues reproduced by the sequence posted by @Gsantomaggio. Our candidate patch introduces a timeout. The rest is still under investigation. |
Does this bug affect RabbitMQ 3.6.1? |
Using HA and ‘auto_delete’ queues, the system gets eventually to a state where some channels don’t have associated connections (shown in the management UI as ‘unknown’) and calls to ‘rabbitmqctl list_channels’ do not return.
This is caused by the queues blocking the channels during the termination, when the rabbit_mirror_queue_master does not return. These are caused by the receive clause in: https://github.com/rabbitmq/rabbitmq-server/blob/stable/src/rabbit_mirror_queue_master.erl#L215
The text was updated successfully, but these errors were encountered: