Skip to content
This repository was archived by the owner on Nov 17, 2020. It is now read-only.

Don't spew stacktrace on join when already member #115

Conversation

binarin
Copy link
Contributor

@binarin binarin commented Jun 30, 2016

Example of stacktrace - rabbitmq/rabbitmq-server#709

binarin pushed a commit to binarin/rabbitmq-server that referenced this pull request Jun 30, 2016
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
@michaelklishin
Copy link
Contributor

I'd use "a member of this cluster" instead of "Properly clustered."

Otherwise 👍.

@binarin binarin force-pushed the rabbitmq-server-fix-join-cluster-when-already-member branch from 5a4ec30 to 03365fc Compare June 30, 2016 16:53
@binarin
Copy link
Contributor Author

binarin commented Jun 30, 2016

Done.

@michaelklishin
Copy link
Contributor

Thank you. This will go into 3.6.4 as the last RC we have planned for 3.6.3 has shipped just a couple of hours ago :(

@michaelklishin michaelklishin merged commit 03365fc into rabbitmq:stable Jul 13, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants