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

Normand Bédard normand.bedard at gmail.com
Thu Nov 28 19:46:28 GMT 2013

I am using RabbitMQ 3.1.5 Erlang R15B03. I have two nodes (Node1 and 
Node2). Both are Disc Type. Also, there is a ha-all policy on my virtual 

When I manually create a queue via the Node1 Web Console, I see the "+1" 
label indicating that my queue is mirrored on the two nodes (Node: Node 1, 
Mirrors: Node 2).

Via the Node 1 Web Console, I manually created a message on the queue. 
After that, from both web consoles, I can access my message from the queue. 

When I reboot the server where Node 2 is hosted, the Node 2 Web Console is 
unreachable, and from the Node 1 Web Console, I can confirm the node is 
down. Still from the Node 1 Web Console, I can access my message from the 
mirrored queue. 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. This is the normal 
behavior. Also from the Node 2 Web Console, I can still access my initial 
message. Everything is fine!

Here is my problem...

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). 

Why this is happening? The message is not supposed to be persisted on each 
nodes when they are mirrored?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131128/ddc292ff/attachment.html>

More information about the rabbitmq-discuss mailing list