[rabbitmq-discuss] All nodes in a cluster becomes unresponsive for a short period of time when any node goes down
tim at rabbitmq.com
Tue May 21 12:15:11 BST 2013
During autohealing, nodes will be restarted dynamically and during the downtime any clients will effectively be disconnected. Those clients may not, however, detect this disconnection in a timely fashion, so I would ask...
1. are you using AMQP heartbeats (to detect disconnections quickly)
2. are you using producer confirms (to clarify that sent message have indeed arrived at the target broker)
3. are you using consumer cancel notifications (to detect that in a clustered + ha setup, the node on which the queue is located has failed/stopped)
On 21 May 2013, at 06:39, thomas wrote:
> I have 3 RabbitMQ nodes, namely rabbit at A, rabbit at b, rabbit at c in a cluster
> with active-mirrored queues HA.
> I am using RabbitMQ 3.1.0 with autoheal chosen for
> "cluster_partition_handling" and "net_ticktime" set to 2. I tried to
> shutdown the network interface instead of shutting down rabbitmq to observe
> the behavior and realized that it results in the temporary unresponsiveness
> of all the other available nodes for a short period of time.
> This was what I did:
> 1) All the 3 nodes are running as per normal
> 2) I shutdown the network interface for rabbit at B
> 3) The other 2 nodes become unresponsive for a short period of time and the
> messages sent during that period were mostly lost.
> I would like to find out if that is the intended behavior or possibly
> something wrong with my setup. Thanks in advance.
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/All-nodes-in-a-cluster-becomes-unresponsive-for-a-short-period-of-time-when-any-node-goes-down-tp26883.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss