Replication bug fixes (backport #516) #521
Merged
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.
Fix bug where occasionally one follower would receive
more entries then expected resulting in triggering 2.
Fix bug when follower received an append_entries_rpc with
no new entries in it would trigger an incorrect resend
scenario when throughput is high.
Fix bug where a late written event could accidentally confirm
unwritten entries in a higher term.
A replication liveness bug that could cause clusters to get stuck
after a member removal.
This is an automatic backport of pull request Replication bug fixes #516 done by Mergify.