Draft
Conversation
jdockerty
force-pushed
the
feat/background-compaction
branch
from
ecf190f to
0ccfd64
Compare
The atomic is not required because the writer is behind a RwLock, so the value is always safe to utilise anyway. The extra abstraction of an atomic is not necessary
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.
Moves the compaction process from being in the hot path of writes, both
setandremove, to a background task on which a compaction notification is received and the job started.A new active log file is created before the compaction notification is sent, so that writes continue to flow.