🐛 fix(ha): fence cross-datacenter transfers - #1859
Merged
Merged
Conversation
Pending placements survived a restart without a durable way to distinguish an abandoned transfer from a live copy. That blocked recovery or risked two owners publishing the same placement. Bind each transfer to the consensus term and a monotonic attempt token. A newer term can reclaim pending work, while stale checkpoints and terminal writes fail their ownership check.
Merging this PR will not alter performance
Comparing 
Footnotes
|
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.
Cross-datacenter replication could preserve a
Pendingplacement across restart without enough ownership evidence to decide whether its transfer was live. That could block recovery or allow competing workers to publish the same placement.Each staged transfer now carries the consensus-term fence and a monotonic attempt token. A live term admits one copy, a newer authoritative term can reclaim abandoned work, and checkpoint or terminal transitions must present the current token. Existing placement records remain readable with a legacy attempt value.
Closes #1517