testdata: add a lagging commit test #137
Merged
+174
−0
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.
This commit adds a test demonstrating the effect of delayed commit on a follower node after a network hiccup between the leader and this follower.
In the described scenario, after the moment of committing an entry on the leader, it takes
HeartbeatInterval + 3/2 * RTT
until the follower learns this entry is committed.This is suboptimal, and could take
HeartbeatInverval + 1/2 * RTT
if the leader didn't cut the commit index atProgress.Match
before sending it to the follower.Informs #138