[rabbitmq-discuss] High availibility in queues

3 views

Skip to first unread message

Gargi, Nikhilesh Prakash

unread,

Nov 25, 2010, 4:45:16 AM11/25/10

to rabbitmq...@lists.rabbitmq.com

Hi,

We are planning to use RabbitMQ in clustering.

If we add 4 RabbitMQ nodes in a cluster, all the credentials, exchanges and bindings get copied to each mnesia db. However, since the queues are specific to nodes, the message directed to a particular queue will be lost (if the node on which that queue was created is down). Is it correct? How can we workaround this? This seems to be a weak link for a High availability solution we need. Are the message will be persisted somewhere and will be delivered to that queue after that particular node comes up?

If the message is gonna lost, can we have a workaround that we create copies of the queues explicitly on each node. Now since they are copies, the exchange will send the message to all the nodes and even if a node is down, message will be delivered to all the copies of that queue.

Thanks & Regards,
Nikhilesh Gargi

_______________________________________________
rabbitmq-discuss mailing list
rabbitmq...@lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Marek Majkowski

unread,

Nov 25, 2010, 6:18:00 AM11/25/10

to Gargi, Nikhilesh Prakash, rabbitmq...@lists.rabbitmq.com

On Thu, Nov 25, 2010 at 09:45, Gargi, Nikhilesh Prakash
<nikhile...@hp.com> wrote:
> We are planning to use RabbitMQ in clustering.
>
> If we add 4 RabbitMQ nodes in a cluster, all the credentials, exchanges and bindings get copied to each mnesia db. However, since the queues are specific to nodes, the message directed to a particular queue will be lost (if the node on which that queue was created is down). Is it correct? How can we workaround this? This seems to be a weak link for a High availability solution we need. Are the message will be persisted somewhere and will be delivered to that queue after that particular node comes up?
>
> If the message is gonna lost, can we have a workaround that we create copies of the queues explicitly on each node. Now since they are copies, the exchange will send the message to all the nodes and even if a node is down, message will be delivered to all the copies of that queue.

Clustering != HA.

Maybe this thread will help:
http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2010-November/010010.html