raft: add backpressure for CommittedEntries flow #60
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
This commit introduces a mechanism for limiting the flow of CommittedEntries that raft pushes through the Ready handling loop. Signed-off-by: Pavel Kalinnikov <[email protected]>
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.
This commit introduces a mechanism for limiting the flow of
CommittedEntriesthat raft pushes through theReadyhandling loop.TODO: describe problem. In short, raft pushes work to be done via
Readyand expects it to be done, there is no backpressure mechanism. In CRDB, for instance, where there are many raft instances per node, many raft loops can push too much work simultaneously and cause out-of-memory situation.TODO: describe solution, and alternatives. There are more complicated alternatives, like making the in-flight limit dynamic, passing an int limit instead of bool, but seemingly the simplest possible bool does the job well.