[rabbitmq-discuss] rabbitmqctl stall/hang when leaving a cluster

[Matt Pietrek]

I've noticed a pattern here that seems to be consistently reproducible.

In our setup, we have three RabbitMQ 2.71 brokers in a cluster on Ubuntu
10.04. They're all mirroring the same set of queues, but that may or may not
be relevant here.

Starting from a healthy state (Management web console showing all brokers,
and all queues in sync), I simply run "rabbitmqctl stop_app" for one of the
nodes, followed by running "rabbitmqctl start_app" on the same node.

The expected results is that the one broker should drop out of the cluster,
then rejoin it. This is indeed what happens when I run against a broker that
does *not* have the stats database (as shown by the Web UI).

If I try this action on the node with the stats database, rabbitmqctl waits
forever and I have to ctrl-c out.  If I then try "rabbitmqctl stop", it
errors out, saying that the node is down.

The only way I can get the cluster back up is to shut down the other two
actively running nodes, then restart all three nodes.

Known issue? Something I'm overlooking? Searching online isn't turning up
anything obvious.

Thanks,

Matt



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120221/8f43f1a7/attachment.htm>