[rabbitmq-discuss] Re-creation of queues not allowed

Arun Suresh arun.suresh at gmail.com
Sun Feb 21 13:48:37 GMT 2010

Thanks for the suggestions guys..

Let me see if i can re-architect it the way u mentioned..


On Sun, Feb 21, 2010 at 6:20 PM, Matthew Sackman <matthew at lshift.net> wrote:

> On Sun, Feb 21, 2010 at 12:11:17PM +0000, Matthias Radestock wrote:
> > In that case simply make the queues non-durable and the messages
> > non-persistent. That way when R1 goes down the queue well and truly
> > disappears and you can re-create it on another node, i.e. your existing
> > logic would work just fine.
> Yup. I was going to suggest not using a cluster, then having both
> consumers create the queues and subscribe on *both* nodes. Then you
> could stick a load balancer or just have a smart producer - provided
> the producer can send a message to one of the two nodes, that message
> well get to one of the clients. This seems to be more what you're
> after - HA rather than scalability.
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100221/7186c600/attachment.htm 

More information about the rabbitmq-discuss mailing list