Repository navigation
Use one durable flush per replacement consensus WAL - #310
Merged
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 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.
Update MatrixRaft to 2cab64e so metadata and chunk checkpoint replacement writes flush the complete temporary WAL once before atomic publication. Normal live WAL appends remain synced before returning. The stable lock, retained suffix and parent-directory sync remain in place.
The dependency extends crash recovery coverage to the boundary before the replacement flush. Syscall tracing verified one replacement-file flush instead of ten for a 9 MiB checkpoint, always before publication. This measures I/O calls rather than throughput.
Validation: 26 metadata/chunk consensus process tests passed with one ignored, 13 checkpoint library tests passed, and the locked all-feature/all-target check passed. File formats and the 256 MiB checkpoint limit are unchanged. Larger file-backed application capture and restoration remain outstanding.