kvcoord: evict range cache on unsplittable batches #119510
Closed
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.
Prototype fix for #119333. Possibly not ideal or backportable, since we can end up evicting range descriptors too often, incurring meta lookup latency.
Maybe we can eagerly refresh the cache here and pay the cost only for the unsplittable requests instead, which are less latency-sensitive (AddSSTable and Barrier).
Epic: none
Release note: None