[rabbitmq-discuss] RabbitMQ clustering issue - exception while stopping the running node

Emile Joubert emile at rabbitmq.com
Mon Oct 7 13:20:47 BST 2013


On 07/10/13 12:01, Rajasekhar P wrote:

> com.rabbitmq.client.ShutdownSignalException: connection error; reason:
> {#method<connection.close>(reply-code=541, reply-text=INTERNAL_ERROR,
> class-id=0, method-id=0), null, ""}

This means an internal error occurred. Please check the broker logfile
and sasl log and let us know what it says.

> 1> How to differenciate master and slave in rabbitmq cluster?

Different queues can have a master on different nodes, so there is no
overall master. "rabbitmqctl list_qeueus name pid" will report the
master as part of the pid field.

> 2> Is there any load balancer do we need ti maintain ?

A load-balancer is not required or prohibited.

> 3> How to dispatch requests to to particular node like below,
>       1-100 queues => Node1
>      101-200 queues => Node2
>      201-300 queues => Node3, etc

By default queues are created on the node that the peer is connected to,
so your application could connect to node1, declare 100 queues, connect
to node2, declare 100 queues and so on. In this way queues will be
distributed across your cluster.

If you want to make sure that requests are distributed evenly then
consider use of the consistent hash exchange:


More information about the rabbitmq-discuss mailing list