raftstore: report busy to PD when restarting if exists apply log lags.#16239
raftstore: report busy to PD when restarting if exists apply log lags.#16239ti-chi-bot[bot] merged 40 commits intotikv:masterfrom
Conversation
Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
Derived from tikv#11859. Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
|
/merge |
|
@overvenus: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 3064494 |
tikv#16239) ref tikv#15874 This pr inspect the gap of each peer's `applied_log_index` and `commit_log_index` when restarting. And if the gap exceeds the `leader_transfer_max_log_lag`, the related peer will be marked as `pending for recovery` state. After the gap is less than `leader_transfer_max_log_lag`, it means that the pending logs is acceptable. Only if the count of ready peers exceeds the given configuration, that is, `min_recovery_ready_region_percent`, this store is ready for re-balancing leaders. Before this stage, the state of this store will be marked `is_busy` to avoid transferring leaders to it. Signed-off-by: lucasliang <nkcs_lykx@hotmail.com> Signed-off-by: dbsid <chenhuansheng@pingcap.com>
tikv#16239) ref tikv#15874 This pr inspect the gap of each peer's `applied_log_index` and `commit_log_index` when restarting. And if the gap exceeds the `leader_transfer_max_log_lag`, the related peer will be marked as `pending for recovery` state. After the gap is less than `leader_transfer_max_log_lag`, it means that the pending logs is acceptable. Only if the count of ready peers exceeds the given configuration, that is, `min_recovery_ready_region_percent`, this store is ready for re-balancing leaders. Before this stage, the state of this store will be marked `is_busy` to avoid transferring leaders to it. Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
|
In response to a cherrypick label: new pull request created to branch |
ref tikv#15874 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ref tikv#15874 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
In response to a cherrypick label: new pull request created to branch |
What is changed and how it works?
Issue Number: Ref #15874
What's Changed:
This pr used to mitigate the dropping trend when rolling restart TiKV nodes, derived from #11859 and #11921.
Related changes
pingcap/docs/pingcap/docs-cn:Check List
Tests
Side effects
Release note