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

[4pt] Make first eventual failover decision disregard membership status #944

Closed
rosik opened this issue Jul 14, 2020 · 0 comments · Fixed by #1644
Closed

[4pt] Make first eventual failover decision disregard membership status #944

rosik opened this issue Jul 14, 2020 · 0 comments · Fixed by #1644

Comments

@rosik
Copy link
Contributor

rosik commented Jul 14, 2020

Proposal form @opomuc.

When we restart whole cluster with eventual failover enabled, it doesn't have time to sync membership status. As a result, every instance thinks he's the only one alive, and becomes a leader an all 100 instances do call init({is_master = true}).

Instead, every instance could make first appointments as in disabled mode, and make decisions immune for some time.

@rosik rosik changed the title Make first eventual failover decision disregard membership status [4pt] Make first eventual failover decision disregard membership status Aug 26, 2020
@kyukhin kyukhin added this to the wishlist milestone Aug 19, 2021
@sergos sergos added teamX and removed teamS Scaling labels Jun 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants