-
Notifications
You must be signed in to change notification settings - Fork 452
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
StateLeft members are never reaped #253
Comments
bwaters
added a commit
to bwaters/memberlist
that referenced
this issue
Jan 5, 2022
Looks like this bug was introduced when StateLeft was implemented. Looks like most places in the code where == StateDead were updated to n.DeadOrLeft() but this one was missed. |
Once a sufficient number of nodes reach the maxPushStateBytes limit then new members are unable to join the consul cluster |
Closed by #254 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unlike StateDead members old nodes that gracefully leave are never reaped. They just permanently increase the node list and sit inside the push/pull state.
Eventually on a large cluster with lots of churn you will hit maxPushStateBytes and push pull stops working completely
The text was updated successfully, but these errors were encountered: