Harden DB writes against partial table loss - #52
Draft
jeanconn wants to merge 2 commits into
Draft
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.
Description
Harden DB writes against partial table loss.
These issues kept popping up in local repro work so collected some solutions.
destroy table state
add_regions()does not reuse IDs whenlast_region_idis absent, stale, or behind the current table contentsregion_idvalues during region-table sync while keepingdestination IDs stable where possible
Interface Impacts
partially replaced state
retired ones during add/sync operations
Testing
for
region_idallocation, stale counters, and sync-time duplicate repairUnit tests
Independent check of unit tests by [REVIEWER NAME]
Functional tests
No functional testing.