[crl-release-21.1] *: Don't block flushes on cleaning turns #1125
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
A flush isn't marked as complete (and flushing set to false) until deleteObsoleteFiles returns. Currently, deleteObsoleteFiles waits for other cleaning turns to complete before doing its own cleaning. This could make flushes wait for cleanup after large compactions, causing write stalls. This change makes flushes move along and mark themselves as completed if a cleaner job is already running, instead of waiting for them. This allows for a lower impact on user-observed write latency.
|
This change is |
petermattis
approved these changes
May 3, 2021
There was a problem hiding this comment.
Reviewable status: 0 of 7 files reviewed, all discussions resolved (waiting on @jbowens)
|
TFTR! |
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.
21.1 backport of #1124.
A flush isn't marked as complete (and flushing set to
false) until deleteObsoleteFiles returns. Currently,
deleteObsoleteFiles waits for other cleaning turns to complete
before doing its own cleaning. This could make flushes wait
for cleanup after large compactions, causing write stalls.
This change makes flushes move along and mark themselves as
completed if a cleaner job is already running, instead of waiting
for them. This allows for a lower impact on user-observed
write latency.