Repository navigation
Conversation
Invalidate table or partition bucket metadata on routing and session failures so a caller-created scanner can resolve the new leader. Preserve existing retry and cleanup behavior; cover rebuilt-scanner recovery with unit tests and a three-node regression.
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.
Purpose
Closes #4909
Fix KV batch scans repeatedly targeting an offline cached leader when callers recreate the scanner using the same Connection and Table.
Brief change log
Tests
Full repository verification and the JDK 8 CI matrix were not run locally.
API and Format
No public API, configuration, RPC protocol, or storage-format changes.
Documentation
No documentation changes.
Generative AI disclosure
Generated-by: OpenAI Codex
Implementation assisted by OpenAI Codex; independently reviewed with DeepSeek.