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

Update serf to pick up graceful leave fix #4278

Merged
merged 1 commit into from
May 10, 2018
Merged

Update serf to pick up graceful leave fix #4278

merged 1 commit into from
May 10, 2018

Conversation

preetapan
Copy link
Contributor

Update serf library for improvements to ensure that leave intents are handled correctly

@@ -1245,6 +1245,10 @@ func (s *Server) setupSerf(conf *serf.Config, ch chan serf.Event, path string) (
}
conf.ProtocolVersion = protocolVersionMap[s.config.ProtocolVersion]
conf.RejoinAfterLeave = true
// LeavePropagateDelay is used to make sure broadcasted leave intents propagate
// This value was tuned using https://www.serf.io/docs/internals/simulator.html to
// allow for convergence in 99.9% of nodes in a 10 node cluster
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused by this comment -- how can there be 99.9% of nodes in a 10 node cluster? (either 90% or 100%?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That serf simulator is based on a convergence factor calculated with logarithmic scale that never reaches 100%, so I didn't round it up for the comment. In practice, for such a small cluster (10 nodes), this means all nodes will converge with this value.

In a 100K node cluster, 99.9% is 99900 nodes, so the fact that its 99.9% and not 100% matters.

@preetapan preetapan merged commit 2eb9c05 into master May 10, 2018
@preetapan preetapan deleted the f-serf-update branch May 30, 2018 20:25
@github-actions
Copy link

github-actions bot commented Mar 3, 2023

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants