MoveMutableSegmentForward should wait until all writes to the previous mutable segment finalized. #100
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
…s mutable segment finalized.
koculu
deleted the
99-bug-the-order-of-opindexes-are-not-guranteed-to-be-incremental-during-mutable-segment-switch
branch
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.
Recently, the internal operation index (op index) per mutable segment was exposed to simplify the replication process. See Issue #93 for more details.
Initially, the op indexes were designed to increment only within the scope of their respective mutable segment. Consequently, when switching between mutable segments, the op index order is not guaranteed to remain incremental.
To ensure consistency, improve the mutable segment switch process to guarantee that the op index order remains incremental across segment transitions.