rabbit_clusterer:status() returns "Clusterer is booting" after a node was restarted due to pause_minority

[kkalin78]

When a node had been paused due to pause_minority and later restored rabbit_clustere:status reports "Cluster is booting". Although the cluster is alive and all nodes including this one are part of the cluster. rabbitmqctl cluster_status shows correct output. I looked at the plugin code and looks like it gets zero notification in this case. RabbitMQ restart is controlled by rabbit itself.

How to reproduce:

1. Build a cluster using the plugin and set pause_minority
2. Using iptables drop connectivity of one node to other cluster members and wait until it pauses
3. Remove iptables rules to restore the connectivity
4. Check that rabbitmqctl eval 'rabbit_clusterer:status().' returns incorrect status.

[michaelklishin]

rabbitmq-clusterer only covers initial cluster formation, not ongoing cluster operations. After the clusterer started cluster nodes, it has absolutely no effect on or awareness of how clustering works.

[kkalin78]

Should I rely on rabbitmqctl cluster_status always even if I use the plugin to assembly the cluster?

[michaelklishin]

@kkalin78 HTTP API or rabbitmqctl, just like before.