kv/client: add incremental scan region count limit (#1899) #1930
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.
This is an automated cherry-pick of #1899
What problem does this PR solve?
This PR adds a token limiter to kv client, in order to control the concurrency of incremental scan region, for some reasons:
What is changed and how it works?
dispatchRequest
intorequestRegionToStore
dispatchRequest
only readssingleRegionInfo
from region channel, try to get gRPC context and sends thesingleRegionInfo
(which has been filled in with gRPC context) into region routerrequestRegionToStore
readssingleRegionInfo
from the output channel of region based region router, and sends real gRPC request to TiKV store.Check List
Tests
Related changes
Release note