Skip to content
This repository has been archived by the owner on Feb 15, 2018. It is now read-only.

Re-joining cluster fails #4

Closed
cap10morgan opened this issue Apr 14, 2015 · 3 comments
Closed

Re-joining cluster fails #4

cap10morgan opened this issue Apr 14, 2015 · 3 comments

Comments

@cap10morgan
Copy link
Contributor

When a node that had been a member of the cluster fails (but does not remove itself from the cluster for whatever reason) and is then brought back up, it cannot successfully re-join the cluster.

Instead I see errors like this:

Already member of cluster: ['rabbit@ip-10-36-136-99','rabbit@ip-10-36-126-31','rabbit@ip-10-36-116-78']

Full transcript of startup log
@gmr
Copy link
Contributor

gmr commented Apr 14, 2015

Hmm, I can see how that could be problematic. I'll take a look ASAP.

gmr added a commit that referenced this issue Apr 14, 2015
@gmr
Dont try and rejoin a clustered node (#4)
1623892
@gmr
Copy link
Contributor

gmr commented Apr 14, 2015

The commit I just made should address the issue. I'm going to add in a few more features and release 0.2.0 which should address this issue.

@gmr gmr closed this as completed Apr 14, 2015
@cap10morgan
Copy link
Contributor Author

Awesome, thanks @gmr!

ValFadeev pushed a commit to ValFadeev/rabbitmq-autocluster that referenced this issue Mar 31, 2017
@michaelklishin
Merge pull request aweber#4 from rabbitmq/rabbitmq-autocluster-62
1017a7a 
Support hostname from nodename in consul using CONSUL_SVC_ADDR_NODENAME
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gmr @cap10morgan