fix(rust_brain): preserve HLC on snapshot restore and gossip receive - #57
Draft
cursor[bot] wants to merge 1 commit into
Draft
fix(rust_brain): preserve HLC on snapshot restore and gossip receive#57cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
restore_from_file() dropped hlc from snapshots and assigned fresh _hlc.now() timestamps, causing TimestampRegression on causal successor writes and silent gossip data loss after disaster recovery. - Add _parse_hlc() for wire/snapshot normalisation - Restore hlc field and advance global HLC during restore - Pass hlc through bulk_write and gossip.receive - Add regression tests for restore round-trip and gossip ordering Co-authored-by: Daniel <DJLougen@users.noreply.github.com>
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.
Bug and impact
restore_from_file()droppedhlcfrom snapshots and assigned fresh_hlc.now()timestamps. After disaster recovery, any causal successor write (or gossip replay with pre-crash HLC) raisesTimestampRegression— silent data loss in replication/gossip paths.Trigger scenario: Node crashes with memory at
hlc=(5000, 10, "nodeA"). After snapshot restore, a peer gossipshlc=(5000, 11, "nodeA")or the node itself writes a causal update. The write is rejected because restore assigned a fresh wall-clock HLC.Root cause
v0.6.0 added HLC monotonic enforcement but
restore_from_file(),bulk_write(), andgossip.receive()never preserved or forwarded HLC timestamps.Fix
_parse_hlc()for wire/snapshot normalisation (with legacy fallback for pre-v0.6.0 snapshots)hlcfield and advance global HLC during restore (under lock)hlcthroughbulk_writeandgossip.receiveValidation
TimestampRegressiontest_restore_preserves_hlc_for_replication, gossip HLC ordering tests