This repository was archived by the owner on Oct 18, 2023. It is now read-only.
multi-tenancy log compaction #553
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 introduces a compaction queue and a snapshot store, to handle replication log compaction.
When a database need to perform a compaction, it first swaps it current replication log file with a new log. The log to compact is placed in the
snapshot_queuedirectory, and it is registered with the persistent compaction queue. A separate thread pop tasks out of the queue, performs the compaction of the log into a partial snapshot, moved the snapshot into thesnapshotsdiretory, and registers the snapshot with the snapshot store.The
SnapshotStore::locatemethod allows for efficient retrieval of a snapshot file for a given database & frame_no.