diff options
| author | Francesco Mazzoli <francesco@rabbitmq.com> | 2012-10-25 14:20:11 +0100 |
|---|---|---|
| committer | Francesco Mazzoli <francesco@rabbitmq.com> | 2012-10-25 14:20:11 +0100 |
| commit | 0198214df35d5a358b2c9ab5561e92083821d86e (patch) | |
| tree | 8f4da560059a4e22f88edac05c417423424bc93a | |
| parent | 822c46a9b8803fdf4e62389a862883eda928b274 (diff) | |
| download | rabbitmq-server-0198214df35d5a358b2c9ab5561e92083821d86e.tar.gz | |
better error message for `join_cluster'
When `force_reset'ing a node, if we want to re-cluster it with the old
cluster `update_cluster_nodes' can be used, but we can't simply use
`join_cluster' again, because the rest of the cluster still thinks the
`force_reset' node is in the cluster.
| -rw-r--r-- | src/rabbit_mnesia.erl | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/rabbit_mnesia.erl b/src/rabbit_mnesia.erl index 53c0da4a..a47bdd4c 100644 --- a/src/rabbit_mnesia.erl +++ b/src/rabbit_mnesia.erl @@ -829,7 +829,9 @@ error_description(resetting_only_disc_node) -> "You cannot reset a node when it is the only disc node in a cluster. " "Please convert another node of the cluster to a disc node first."; error_description(already_clustered) -> - "You are already clustered with the nodes you have selected."; + "You are already clustered with the nodes you have selected. If the " + "node you're trying to cluster with is not present in the current node " + "status, use 'upgrade_cluster_nodes'."; error_description(not_clustered) -> "Non-clustered nodes can only be disc nodes."; error_description(cannot_connect_to_cluster) -> |