CASSSIDECAR-486: Prefer exact-range CDC checkpoint on load to avoid restart rewind - #372
Open
Klose6 wants to merge 1 commit into
Open
CASSSIDECAR-486: Prefer exact-range CDC checkpoint on load to avoid restart rewind#372Klose6 wants to merge 1 commit into
Klose6 wants to merge 1 commit into
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
2 participants
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.
On sidecar restart, CDC consumers reload checkpoint state from sidecar_internal.cdc_state_v2. Today loadStateForRange returns all rows whose (start, end) overlaps the owned range, then analytics merges them with Marker.min (earliest segment/offset wins), which can rewind the offset to days ago. However when an exact match exists, we can ignore stale overlapping historical rows in cdc_state_v2, and fall back to the existing overlap-based load (needed for cluster shrink) when no exact match is found.