-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Question: add member without change the quorum #10329
Comments
@JTrotta adding members will increase quorum. We are working on leaner nodes where if you add a new learner they are non voting members and would not increase quorum. These learners can later be promoted to full members. https://github.com/etcd-io/etcd/blob/master/docs/server-learner.rst We have also added --strict-reconfig-check This flag will prevent configuration change that would result in loss of quorum. This I believe resolves #3477.
I think in this case the problem is that the current client balancer is not working as expected. We are working to resolve this so if a down node is in the member list client will failover to next member. #6420 is still open but the solution is for etcd server to not add a member who has been misconfigured or not started. This eventually will increase quorum for a new member. |
@hexfusion I understand your points. But does this means that the cluster has no fault tolerance at all? |
Not sure I follow if you have 3 member cluster and one goes down then the cluster is still quorate. Quorum in a 3 node cluster is 2. So the down node will not respond directly but other 2 members will. ref: https://github.com/etcd-io/etcd/blob/master/Documentation/faq.md#what-is-failure-tolerance |
You're right. With 3 members (2 working, 1 fault) it works. With 2 members (1 working, 1 fault), it doesn't work. |
Hello,
it's not clear to me if #3477 or #6420 have been solved.
My problem is that I do not want to increase quorum adding new members. The quorum should be fixed to the initial one, this way an ETCD client can always connects to any alive member and adjusts the lost node membership.
I'm using CentOS 3.2.22 version
The text was updated successfully, but these errors were encountered: