diff options
| author | Simon MacMullen <simon@rabbitmq.com> | 2014-07-03 14:59:08 +0100 |
|---|---|---|
| committer | Simon MacMullen <simon@rabbitmq.com> | 2014-07-03 14:59:08 +0100 |
| commit | 808473257bb974f394e8b940d3ae9859f892fe76 (patch) | |
| tree | d1e8810fc45b073009a8f02f2f15ac0f910afd13 /docs | |
| parent | c2e262c6d17d4f649c2590022fe387fbf622abd1 (diff) | |
| download | rabbitmq-server-git-808473257bb974f394e8b940d3ae9859f892fe76.tar.gz | |
Tweak text.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/rabbitmqctl.1.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml index 8882bd6ba0..43d1e55a1b 100644 --- a/docs/rabbitmqctl.1.xml +++ b/docs/rabbitmqctl.1.xml @@ -464,21 +464,21 @@ Normally when you shut down a RabbitMQ cluster altogether, the first node you restart should be the last one to go down, since it may have seen things - happen that other nodes did not. However, sometimes + happen that other nodes did not. But sometimes that's not possible: for instance if the entire cluster loses power then all nodes may think they were not the last to shut down. </para> <para> - In such a case you can use <command>rabbitmqctl + In such a case you can invoke <command>rabbitmqctl force_boot</command> while the node is down. This will tell the node to unconditionally start next time you ask it to. If any changes happened to the cluster after this node shut down, they will be lost. </para> <para> - If the last node to go down is lost then you should use - <command>rabbitmqctl forget_cluster_node + If the last node to go down is permanently lost then you + should use <command>rabbitmqctl forget_cluster_node --offline</command> in preference to this command, as it will ensure that mirrored queues which were mastered on the lost node get promoted. |