[rabbitmq-discuss] RabbitMQ cluster w/ .Net client

Mon May 23 20:15:35 BST 2011

Hi,

I've read many posts and blogs at this point and I'm still not sure
about how to cluster correctly my 2 RabbitMQ nodes.

I've read the RabbitMQ clustering guide:
http://www.rabbitmq.com/clustering.html
<http://www.rabbitmq.com/clustering.html> 

I found out about a mysterious ClusterId in the API guide, with no
explanation on how to get that Id in the first place:
http://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v2.4.1/rabbitmq-
dotnet-client-2.4.1-api-guide.pdf
<http://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v2.4.1/rabbitmq
-dotnet-client-2.4.1-api-guide.pdf> 

Learned in that StackOverflow post that basically I'd need my clients to
be aware of each node in the cluster and code for failover scenario:
rabbitmq HA cluster
<http://stackoverflow.com/questions/4140653/rabbitmq-ha-cluster> 

Now... The behavior I'd like to have is something a little more
transparent if possible. Where I would potentially use that "ClusterId"
on the client to make the consumer cluster aware and then hopefully the
library knows to randomly connect to either node to grab messages.

Granted I know a message can only be on one server at a time, so I'm
hoping for some round robin magic from the DotNet client library that
would also handle fail over situations.

What I was hoping also from a publisher perspective is that the exchange
would round robin distribute messages to the various nodes in the
cluster. The exchange would also be cluster aware and handle fail over
situations gracefully.

Basically I was hoping for the whole thing to scale without changing any
code or configuration on the publisher or consumer apps.

Now based on my readings it doesn't quite work like that... unless I
missed something. If my knowledge is up to date and I have to code all
that cluster aware business, then... why does RabbitMQ have a cluster
feature in the first place? How is it used?

Is there a way to have that kind of behavior out of RabbitMQ without
coding that much?

Thanks

Yann

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110523/c063afec/attachment-0001.htm>