[rabbitmq-discuss] Mirrored Queue Failover takes longer than expected

[robin.cox at esendex.com]

Hi,

I am currently testing out some RabbitMQ cluster configurations and have 
come across some behaviour that is undesirable in an otherwise useful set 
up.
The amount of time the cluster takes to promote a mirrored slave queue to 
become the master seems quite long.

I have a cluster with two instances of RabbitMQ sat behind a load balancer 
in order to handle reconnection when one of the boxes fails. 
I have a publisher publishing persistent messages to a durable mirrored 
queue.
If one box dies, the publisher will attempt to reconnect via the load 
balancer. The load balancer, knowing one box is down, directs the traffic 
to the healthy RabbitMQ instance.
This reconnection is very fast, however, when attempting to publish to the 
healthy RabbitMQ exceptions are thrown for a period of between 40-80 
seconds before messages are published as normal again.

Has anyone else experienced similar behaviour when using RabbitMQ 
clustering in this way? Ideally, the failover time for my implementation 
needs to be negligible. 

Having implemented this using both the .NET and Java SDKs I believe I have 
ruled out the implementation of the SDKs being the cause.
I have also run tests that do not use the load balancer to be sure it isn't 
the cause of the issue so my current understanding is that this must be a 
limitation of RabbitMQ.

If anyone has any knowledge they can share on this topic I would greatly 
appreciate it.

Cheers

-- 
Confidentiality: This e-mail (and any associated files) is intended only 
for the use of the intended recipient and may contain information that is 
confidential, subject to copyright or constitutes a trade secret. If you 
are not the intended recipient you are hereby notified that any disclosure, 
copying or distribution of this message, or files associated with this 
message, is strictly prohibited. If you have received this message in 
error, please notify us immediately by replying to the message and then 
delete it from your computer. Messages sent to and from us may be 
monitored. The views expressed in this message are those of the author and 
do not necessarily represent the views of Esendex Ltd.

Security: This e-mail and any attachments are believed to be free from any 
virus but it is the responsibility of the recipient to ensure this is so. 
E-mail is not a 100% secure communications medium. We recommend you observe 
this when e-mailing us.

Esendex Ltd is a limited company registered in the UK, with company number 
04217280 and having its registered office at 15 Warwick Road • Stratford 
Upon Avon • Warwickshire • CV37 6YW.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130926/91544d59/attachment.htm>