Skip to content
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

#6 - ensures better resiliency and moves joining to initialisation. #7

Closed
wants to merge 4 commits into from

Conversation

ajohnstone
Copy link

@ajohnstone ajohnstone commented Jan 21, 2017

@casa87
Copy link

casa87 commented Feb 15, 2017

Nice, thank you I was struggling after a reboot due to new IP and this fixed this part, but I am still getting the following error :
2017/02/15 23:19:22 [ERR] agent: coordinate update error: No cluster leader 2017/02/15 23:19:25 [ERR] raft: Failed to take snapshot: nothing new to snapshot 2017/02/15 23:19:33 [ERR] raft: Failed to take snapshot: nothing new to snapshot 2017/02/15 23:19:39 [ERR] raft: Failed to take snapshot: nothing new to snapshot

Any idea on how to fix this step would be awesome

@ajohnstone
Copy link
Author

ajohnstone commented Feb 15, 2017

On complete cluster failure ips change and raft fails. The above solves a number of problems, however I have yet to solve this last part, one suggestion I had was to use a service for each pod.

Although I have yet to try this or find an alternative solution.

For reference: hashicorp/consul#457

@kelseyhightower
Copy link
Owner

Using Kubernetes auto joining as define in the docs.

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.

Testing failing nodes does not restore the cluster....
3 participants