Problem:- The network split has occured in the Rabbitmq cluster causing the cluster of node1, node2 and node3 divide in two. Also the erlang process count was continuously high and hitting the upper limit. Further on network split the main cluster node hang up.
Cause:- The network split and high erlang process count might have occured if the request are not equally split across different nodes rather application is using one server as its endpoint. Due to which the erlang process count was continuously high on the node and that node got hanged , even it was hard to restart the process again.
Resolution:-
1. As network split occurs you need to stop the rabbitmq across all the nodes using the following command.
service rabbitmq-server stop
2. After that you have to first start the node whose cookie was used across the other nodes. In our case node3 cookie was used across node1 and node2 to create the rabbitmq cluster. So we started the node3 first and than we remaining nodes
cd /var/lib/rabbitmq/mnesia/
mkdir -p /tmp/mnesia
mv * /tmp/mnesia/
service rabbitmq-server start
service rabbitmq-server stop
cd /var/lib/rabbitmq/mnesia/
mkdir -p /tmp/mnesia
mv * /tmp/mnesia/
service rabbitmq-server start
rabbitmqctl stop_app
rabbitmqctl reset
rabbitmqctl join_cluster rabbit@node3
rabbitmqctl start_app
rabbitmqctl cluster_status
0 comments:
Post a Comment