-
Notifications
You must be signed in to change notification settings - Fork 688
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update TiKV store status information #6949
Update TiKV store status information #6949
Conversation
[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. Reviewer can indicate their review by submitting an approval review. |
@nolouch: 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. In 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. |
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
@en-jin19 And please fix the checkbox syntax in the PR description box, and make it consistent with the label used for this PR. |
faq/deploy-and-maintain-faq.md
Outdated
@@ -266,6 +266,10 @@ PD can tolerate any synchronization error, but a larger error value means a larg | |||
|
|||
The client connection can only access the cluster through TiDB. TiDB connects PD and TiKV. PD and TiKV are transparent to the client. When TiDB connects to any PD, the PD tells TiDB who is the current leader. If this PD is not the leader, TiDB reconnects to the leader PD. | |||
|
|||
#### What is the relationship between each status (Up, Disconnect, Offline, Down, Tombstone) of a TiKV store? | |||
|
|||
You can use PD Control to check the status information of a TiKV store. For the relationship between each status, refer to [Relationship between each status of a TiKV store](/tidb-scheduling.md#information-collection). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这个图表示的各状态之间的关系其实不是特别清晰的,适合用作为辅助材料。
另外,为了直接回答标题问题,感觉可以把两句的顺序调换过来。毕竟如果解释了关系,可能也有人会好奇那要看这些关系需要怎么操作。
Co-authored-by: shichun-0415 <89768198+shichun-0415@users.noreply.github.com>
/remove-status LGT1 |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 5b27776
|
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #7998. |
In response to a cherrypick label: new pull request created: #7999. |
In response to a cherrypick label: new pull request created: #8000. |
In response to a cherrypick label: new pull request created: #8001. |
In response to a cherrypick label: new pull request created: #8002. |
In response to a cherrypick label: new pull request created: #8003. |
What is changed, added or deleted? (Required)
Added the relationship between a TiKV store in "faq/deploy-and-maintain-faq.md", "pd-control.md", and "tidb-scheduling.md".
Which TiDB version(s) do your changes apply to? (Required)
Although most of Chinese PRs are only applied to master, newly updated PR #8723 updated the contents from v4.0 to master, for consistency, this PR will be also applied to the corresponding versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?