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

Unhealthy cluster after removing a peer in 2 node cluster #332

kshlm opened this Issue Jun 29, 2017 · 2 comments


None yet
3 participants
Copy link

kshlm commented Jun 29, 2017

(Only valid once #324 is merged)
Deleting the 2nd peer in a 2 node cluster will leave the 1st node unresponsive. This happens when using the embedded elastic store.

This happens because the etcd instance is left without quorum to operate when the 2nd peer leaves. With 3 or more peers, the etcd cluster still has quorum and can continue to serve requests.

Solving this requires changes to elasticetcd and the deletepeer code, to introduce special cases for handling deletes in a 2node cluster.


This comment has been minimized.

Copy link

prashanthpai commented Jun 29, 2017

Related to issue #323 ?


This comment has been minimized.

Copy link

atinmu commented Nov 28, 2017

Is this issue still valid?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment