[rabbitmq-discuss] RabbitMQ 3.2.2 durable queue failover

Simon MacMullen simon at rabbitmq.com
Tue Feb 25 10:34:15 GMT 2014

This is the behaviour you would expect to see if the queue were not 
defined as mirrored - did you set up a policy for mirroring per 
http://www.rabbitmq.com/ha.html#genesis ?

Cheers, Simon

On 24/02/2014 19:57, Andy Martin wrote:
> I am testing failover before putting my RabbitMQ implementation into
> production. When I bring down one RabbitMQ node I start getting the
> following error:
> RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP
> operation was interrupted: AMQP close-reason, initiated by Peer,
> code=404, text="NOT_FOUND - home node 'rabbit at DEVRABBIT01' of durable
> queue 'QUEUE_TEST' in vhost '/' is down or inaccessible", classId=50,
> methodId=10, cause=
> I am running RabbitMQ 3.2.2 with Erlang R16B03.
> DEVRABBIT01 is the node that has been shut down.
> DEVRABBIT02 is the node that is still running and that the client is
> connected to.
> Both are disc nodes. The named queue (QUEUE_TEST) does not appear in the
> management console on the running node.
> It looks like this was supposed to have been fixed in 2.4.0. Any reason
> I would be seeing this in 3.2.2?
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list