pdpb: add store scheduling state to GetStore response - #1503
Open
LykxSassinator wants to merge 1 commit into
Open
LykxSassinator wants to merge 1 commit into
LykxSassinator wants to merge 1 commit into
Conversation
Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
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.
Summary
Issue: ref tikv/client-go#2012
StoreSchedulingStatetoGetStoreResponsefor PD-owned, per-store scheduling decisions used by clients during replica selection.evicted_as_slow_store, aligned with PD's recovery-time-based slow-store eviction decision and distinct from local health observations or store lifecycle metadata.GetStoreResponse, avoiding pollution of the sharedmetapb.Storemetadata path.false, and reserve the message for independent future constraints such as slow-trend or stopping-store eviction.proto.lock.Tests