fix the description about the slow score range of slow stores#6871
Conversation
Signed-off-by: 5kbpers <tangminghua@pingcap.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. |
|
@rleungx: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments. DetailsIn response to this: Instructions 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. |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 813e7dd |
|
/hold |
| 实践中,如果能确定这个节点的故障是不可恢复的,可以立即做下线处理,这样 PD 能尽快补齐副本,降低数据丢失的风险。与之相对,如果确定这个节点是能恢复的,但可能半小时之内来不及,则可以把 `max-store-down-time` 临时调整为比较大的值,这样能避免超时之后产生不必要的副本补充,造成资源浪费。 | ||
|
|
||
| 自 v5.2.0 起,TiKV 引入了慢节点检测机制。通过对 TiKV 中的请求进行采样,计算出一个范围在 1~100 的分数。当分数大于 80 时,该节点会被设置为 Slow 状态。可以通过添加 `evict-slow-store-scheduler` 来针对慢节点进行对应的检测和调度,目前支持当且仅当出现一个慢节点时,将慢节点上的 leader 全部驱逐(其作用类似于 `evict-leader-scheduler`)。 | ||
| 自 v5.2.0 起,TiKV 引入了慢节点检测机制。通过对 TiKV 中的请求进行采样,计算出一个范围在 1~100 的分数。当分数大于等于 80 时,该节点会被设置为 Slow 状态。可以通过添加 `evict-slow-store-scheduler` 来针对慢节点进行对应的检测和调度,目前支持当且仅当出现一个慢节点时,将慢节点上的 leader 全部驱逐(其作用类似于 `evict-leader-scheduler`)。 |
There was a problem hiding this comment.
搜索了一下,当前文档中没有 evict-slow-store-scheduler 的说明,能否在这个 PR 中补充一下呢?
@5kbpers
There was a problem hiding this comment.
目前对于 scheduler 的描述似乎都在这个文档里
There was a problem hiding this comment.
Signed-off-by: 5kbpers <tangminghua@pingcap.com>
Signed-off-by: 5kbpers <tangminghua@pingcap.com>
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 5c6373b |
Signed-off-by: 5kbpers tangminghua@pingcap.com
What is changed, added or deleted? (Required)
fix the description about the slow score range of slow stores
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?