WIP: Randomize ranges in non primary update - #841
Open
lejeunerenard wants to merge 4 commits into
Open
Conversation
Ensures unfulfillable ranges can't block the update by gathering at the front of a large list of pending ranges.
Credit to @marcus-pousette-hp for two of the test. Skipped one as it was for a different solution but might be necessary as discussions progress. Included a test for seeks being blocked by ranges.
This is trying to ensure that the replicator doesn't get stuck idle when it could be doing work / requesting.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR is a sketch of ensuring range requests get resolved more reliably by randomizing which are being resolved when updating non-primary.