Skip to content

Report join_cluster errors more thoroughly #868

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

binarin
Copy link
Contributor

@binarin binarin commented Jun 30, 2016

Because {ok, _} should mean OK, and {error, _} should be a real error.

mnesia_lib:all_nodes() is used by mnesia:info() even when mnesia is not running, so I think it's an appropriate function to call.

With the addition of
rabbitmq/rabbitmq-common#115
rabbitmqctl join_cluster will become idempotent, fixing #709.

Because `{ok, _}` should mean OK, and `{error, _}` should be a real error.

With the addition of
rabbitmq/rabbitmq-common#115
`rabbitmqctl join_cluster` will become consistent.
@michaelklishin michaelklishin self-assigned this Jun 30, 2016
@michaelklishin michaelklishin added this to the 3.6.4 milestone Jun 30, 2016
binarin pushed a commit to binarin/rabbitmq-autocluster that referenced this pull request Jul 1, 2016
Joining cluster may fail, so we need to handle failure according to
`autocluster_failure` setting.

Before rabbitmq/rabbitmq-server#868 even `{ok,
already_member}` should be treated as an error, but I'm not so sure
about this.
@michaelklishin michaelklishin merged commit 1e3810a into rabbitmq:stable Jul 13, 2016
binarin pushed a commit to binarin/rabbitmq-server that referenced this pull request Jul 29, 2016
Forgot to update specs in rabbitmq#868
@binarin binarin mentioned this pull request Jul 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants