Fix stale consistent read result after server restart #342
Conversation
This file contains hidden or 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
kjnilsson
changed the title
As if there had been a leader change before this could reset to true even before the leader has fully applied it's noop command for the new term. This could result in occasional stale consistent read results.
kjnilsson
force-pushed
the
stale-read-redux
branch
from
870fa70 to
cc79766
Compare
kjnilsson
changed the title
Contributor
Author
|
I ran the |
michaelklishin
approved these changes
Dec 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Reset cluster_change_permitted when becoming leader
As if there had been a leader change before this could reset to true
even before the leader has fully applied it's
noopcommand for the newterm. This could result in occasional stale consistent read results.