-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add term check on the internal streams, to avoid wrong closures of leader controller #513
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Coordinator logs
Oxia-1 (old-leader)
Oxia-2 (new leader)
The replicate request (in term 4) from |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During a leader election, an old leader can force back the new leader into a follower mode.
This does not affect the correctness (eg: the old leader's requests are then ignored because the term is invalid), though it causes the shard to be unavailable until a new leader election is triggered.
The simplified sequence is like:
oxia-1
is the old leader in term: 4oxia-0
andoxia-2
are fenced correctly, while oxia-1 is ignored, and will be retried in backgroundoxia-2
is elected leader (term: 5)oxia-1
is still running the leader controller (because it never got successfully fenced), and it keeps trying to replicated tooxia-0
andoxia-2
.The replicate requests keep failing (because the term has already changed to 5), though the first request has the effect of putting oxia-2 back in follower mode.
We are now in a state where coordinator is happy thinking
oxia-2
as the leader, thoughoxia-2
went back to follower mode. A new leader election is not triggered becauseoxia-2
looks healthy overall (the health check is done at the pod level, not at shard level).