grafana: supply the explanation on the metrics of Flow-Control in TiKV. #15720
Conversation
qiancai
added
needs-cherry-pick-release-6.5
ti-chi-bot
bot
added
the
size/XS
ti-chi-bot
bot
added
size/S
…i/docs into supply_flow_control-15670
Co-authored-by: lucasliang <[email protected]>
[LGTM Timeline notifier]Timeline:
|
|
@LykxSassinator: adding LGTM is restricted to approvers and reviewers in OWNERS files. 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 kubernetes/test-infra repository. |
Co-authored-by: lucasliang <[email protected]> Co-authored-by: Aolin <[email protected]>
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| - Txn command throttled duration: The blocked duration for commands related to transactions due to throttling. Under normal circumstances, this metric is 0. | ||
| - Non-txn command throttled duration: The blocked duration for other commands due to throttling. Under normal circumstances, this metric is 0. |
There was a problem hiding this comment.
最后这两个，Txn command throttled duration、Non-txn command throttled duration 截图中没有
There was a problem hiding this comment.
updated it in https://github.com/pingcap/docs/pull/15765/files
|
In response to a cherrypick label: new pull request created to branch |
| ### Flow Control | ||
|
|
||
| - Scheduler flow: The scheduler traffic on each TiKV instance in real time. | ||
| - Scheduler discard ratio: The rejection ratio of scheduler requests on each TiKV instance. If this ratio is greater than 0, it indicates that flow control exists. When `Compaction pending bytes` exceeds its threshold, TiKV will linearly increase the `Scheduler Discard Ratio` based on the exceeded portion. The client will retry the rejected requests automatically. |
There was a problem hiding this comment.
| - Scheduler discard ratio: The rejection ratio of scheduler requests on each TiKV instance. If this ratio is greater than 0, it indicates that flow control exists. When `Compaction pending bytes` exceeds its threshold, TiKV will linearly increase the `Scheduler Discard Ratio` based on the exceeded portion. The client will retry the rejected requests automatically. | |
| - Scheduler discard ratio: The rejection ratio of scheduler requests on each TiKV instance. If this ratio is greater than 0, it indicates that flow control exists. When `Compaction pending bytes` exceeds its threshold, TiKV will linearly increase the `Scheduler discard ratio` based on the exceeded portion. The client will retry the rejected requests automatically. |
There was a problem hiding this comment.
|
In response to a cherrypick label: new pull request created to branch |
|
In response to a cherrypick label: new pull request created to branch |
|
In response to a cherrypick label: new pull request created to branch |
|
In response to a cherrypick label: new pull request created to branch |
This pr supplements the explanation on the Flow-Control metrics in Tikv-Details part.
First-time contributors' checklist
What is changed, added or deleted? (Required)
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?