-
Notifications
You must be signed in to change notification settings - Fork 2
adapter: Fence Redis reads before snapshots #1167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
cbc99dd
adapter: Fence Redis reads before snapshots
bootjp 0ae2c34
adapter: Use lease fences for Redis EXEC reads
bootjp a171f46
adapter: Route Redis read fences by shard leader
bootjp a9b26b9
adapter: Fail closed on mixed Redis read-fence leaders
bootjp 86cd4f0
adapter: Fence Redis range reads across shards
bootjp 257d4b5
adapter: Retry Redis read fences on route changes
bootjp 09a0e49
adapter: Pin Redis read-fence route versions
bootjp cf73c96
adapter: Preserve Redis read-fence route pins
bootjp 8496aa7
adapter: Tighten Redis EXEC retry fences
bootjp b36da7a
adapter: Close Redis read-fence review gaps
bootjp 94fb695
test: Tighten Redis read-fence review coverage
bootjp d2951fb
adapter: Close Redis read-fence edge cases
bootjp a5a5520
test: Cover list scan prefix extraction
bootjp 4ed6cae
adapter: Route literal Redis keys safely
bootjp ae80151
kv: Preserve empty Redis route keys
bootjp File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a legal zero-length Redis key, this produces
!redis|route|, butkv.redisRouteKeyrejects keys with no bytes after the final separator, so the representative routes by the wrapper bytes rather than by the empty logical key. Empty-key storage representatives such as!redis|str|are likewise left as distinct raw prefixes; in a sharded catalog where those prefixes belong to different groups, evenMULTI; GET ""; EXECcan appear to span multiple leaders and fail withERR EXEC read fence spans multiple shard leaders, while standalone proxy checks can select a group different from the stored row. Encode empty keys unambiguously or make routing distinguish a successfully decoded empty key from decode failure.Useful? React with 👍 / 👎.