[rabbitmq-discuss] Network partition detected, did not recover gracefully even though cluster_partition_handling = autoheal

Nicholas Stuart nicholasastuart at gmail.com
Tue Dec 10 18:17:13 GMT 2013

I received a message regarding my cluster state saying "Network partition 
detected". I went to check my RabbitMQ logs and I can see a bunch of error 
reports like this:

=ERROR REPORT==== 7-Dec-2013::08:46:18 ===
** Generic server <0.507.0> terminating
** Last message in was {'DOWN',#Ref<>,process,<7022.1390.0>,
** When Server state == {state,
** Reason for termination == 
** {function_clause,[{orddict,fetch,

After restarting the troubled node, which fixed the network partition 
message, I see the following message in my logs many times:

Discarding message {'$gen_call',{<0.26793.8>,#Ref<>},stat} from 
<0.26793.8> to <0.433.0> in an old incarnation (3) of this node (2)

I'm not sure why it failed, but I did have some network failure indicated 
in other systems, so I assume it was that. My issue is that the network 
never tried to rescue itself afterwards, even though in my rabbitmq.conf I 
have cluster_partition_handling set to autoheal. It is my understanding 
that setting it to autoheal will cause the nodes to fix its network 
partition, is this assumption incorrect?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131210/b3a15dd9/attachment.html>

More information about the rabbitmq-discuss mailing list