[rabbitmq-discuss] HA Clustering fails to keep message when node turn down.

Simon MacMullen simon at rabbitmq.com
Fri Nov 29 09:42:15 GMT 2013


On 28/11/2013 19:46, Normand Bédard wrote:
> When the Node 2 server is back online, I see that
> the nodes are not synchronized, meaning that new messages arrived on
> Node 1 during the Node 2 shutdown won't be replicated on Node 2.

*And* that any messages that were on node 2 before it shut down have 
been lost (since node 2 has no way of knowing what node 1 has done with 
them while it was down, it can't just keep all of them).

> When I reboot the Node 1 server, I observe all the same behaviors as in
> my previous test where I shutdown Node 2 server, but during the time the
> Node 1 is down, there is no messages available from the Node Web Console
> (but the queue is still accessible).

...so now the messages are lost on node 2 and node 1.

See http://www.rabbitmq.com/ha.html#unsynchronised-slaves and 
http://www.rabbitmq.com/ha.html#eager-synchronisation

Cheers, Simon


More information about the rabbitmq-discuss mailing list