[rabbitmq-discuss] HA Queues lost when a node dies
francesco at rabbitmq.com
Mon May 7 18:06:15 BST 2012
It's hard to tell what happened without looking at the logs and without
knowing your setup; but a number of severe bugs related to HA were fixed
in 2.8.2, so it's definitely worth a try.
If the situation does not improve, please post more details on the list.
On 07/05/12 17:44, Bozhidar Bozhanov wrote:
> We are currently trying to run RabbitMQ (2.8.1) in a cluster and use
> highly-available queues. We have around 50 queues. Each queue is
> registered with one of the nodes (at random), as master, and using
> x-ha-policy=all. We have 2 nodes in the cluster.
> The management console shows that the cluster is successfully created,
> and that the queues are highly-available and properly mirrored. Then
> we kill one of the nodes (with kill -9) to simulate system failure. We
> have tried this five times, and each time a different result was
> - only 1 queue 'survived' (the metadata about the others was deleted
> and they were not visible in the management console, nor we could send
> or consume messages to/from them)
> - all but 3 queues survived
> - only 10 queues survived
> - all queues survived
> - all but 1 queue survived
> The queues that survived properly switched their master node to the
> only remaining one.
> The results are random, as it seems. Is this expected behaviour? Is it
> likely to be fixed in 2.8.2. And how can we make sure that if a node
> dies, the queues don't get deleted.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss