Caution
We recommend that you do not restart a RabbitMQ node on a production environment by executing systemctl restart rabbitmq-server since a cluster can become inoperative.
To restart a single RabbitMQ node:
Gracefully stop rabbitmq-server on the target node:
systemctl stop rabbitmq-server
Verify that the node is removed from the cluster and RabbitMQ is stopped
on this node:
rabbitmqctl cluster_status
Example of system response:
Cluster status of node rabbit@msg01
[{nodes,[{disc,[rabbit@msg01,rabbit@msg02,rabbit@msg03]}]},
{running_nodes,[rabbit@msg03,rabbit@msg01]}, # <<< rabbit stopped on msg02
{cluster_name,<<"openstack">>},
{partitions,[]},
{alarms,[{rabbit@msg03,[]},{rabbit@msg01,[]}]}]
Start rabbitmq-server:
systemctl start rabbitmq-server