Comment 5 for bug 1714150

Revision history for this message
Ignatious Johnson Christopher (ijohnson-x) wrote :

From: Pramodh D'Souza
Date: Wednesday, September 20, 2017 at 3:05 AM
To: Vedamurthy Ananth Joshi
Cc: Rudra Rugge , Sachchidanand Vaidya , Yuvaraja Mariappan , Chhandak Mukherjee
Subject: Re: Bug 1714150

Hi Vedu,

The issue is that there are two rabbit clusters. The rabbit configuration files seem to have been modified after starting the nodes.
You can try restarting to have them read the updated configuration.

Node 1
root@nodec1(controller):/# rabbitmqctl cluster_status
Cluster status of node rabbit@nodec1 ...
[{nodes,[{disc,[rabbit@nodec1,rabbit@nodec2]}]},
 {running_nodes,[rabbit@nodec2,rabbit@nodec1]},
 {cluster_name,<<"<email address hidden>">>},

Cluster status of node rabbit@nodec2 ...
[{nodes,[{disc,[rabbit@nodec1,rabbit@nodec2]}]},
 {running_nodes,[rabbit@nodec1,rabbit@nodec2]},
 {cluster_name,<<"<email address hidden>">>},
 {partitions,[]}]

root@nodec3(controller):/# rabbitmqctl cluster_status
Cluster status of node rabbit@nodec3 ...
[{nodes,[{disc,[rabbit@nodec3]}]},
 {running_nodes,[rabbit@nodec3]},
 {cluster_name,<<"<email address hidden>">>},
 {partitions,[]}]

The reason you see it on node2 and node3 is because they stopped receiving rabbit messages when they got split into a different rabbit cluster.

Regards,
Pramodh