pd: document CPU-aware hot region scheduling#21758
Open
qiancai wants to merge 8 commits into
Open
Conversation
qiancai
added
area/scheduling
ti-chi-bot
Bot
added
the
size/XS
Synced from: pingcap/docs#23140 Target PR: pingcap#21758 AI Provider: azure Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
|
Auto-sync completed successfully Source PR: pingcap/docs#23140 Chinese documentation has been updated based on English documentation changes. |
|
[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 |
ti-chi-bot
Bot
added
size/M
qiancai
commented
Jul 2, 2026
qiancai
commented
Jul 2, 2026
qiancai
commented
Jul 2, 2026
qiancai
commented
Jul 2, 2026
qiancai
commented
Jul 2, 2026
lhy1024
reviewed
Jul 2, 2026
Comment on lines
+179
to
+185
|
|
||
| 从 v8.5.7 和 v9.0.0 开始，针对读热点，PD 支持基于 TiKV CPU 使用情况的热点 Region 调度。TiKV 在 Store 心跳中上报每个 Region 的读 CPU 使用情况，PD 可将 CPU 使用情况作为调度维度之一。该机制有助于 PD 识别出那些 QPS 或字节吞吐量看似均衡、但 TiKV CPU 使用量仍不均衡的读热点，例如包含不同 CPU 开销的负载，或不同 TiKV 节点处理不同负载模式的集群。 | ||
|
|
||
| - 对于支持上报读 CPU 使用情况的集群，`balance-hot-region-scheduler` 的默认 `read-priorities` 值为 `cpu,byte`。 | ||
| - 对于不支持上报读 CPU 使用情况的集群，PD 会自动回退到 `query,byte`；如果集群也不支持 `query` 维度，则回退到 `byte,key`。 | ||
|
|
||
| 如需查看或调整调度维度，请使用 [`pd-ctl scheduler config balance-hot-region-scheduler`](/pd-control.md#scheduler-config-balance-hot-region-scheduler)。 |
Co-authored-by: lhy1024 <lhylhy1024@gmail.com>
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
2 participants
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.
This PR is translated from: pingcap/docs#23140
What is changed, added or deleted? (Required)
Document CPU-aware Hot Region scheduling for read hotspots introduced in v8.5.7:
flow_cpuandcpu-read-rateoutput descriptions forpd-ctl hot.min-hot-cpu-rate,cpu-rate-rank-step-ratio, and CPU-awareread-prioritiesbehavior forbalance-hot-region-scheduler.Store read cpupanel description in the PD Grafana dashboard doc.Which TiDB version(s) do your changes apply to? (Required)
Need cherry-pick to
release-8.5because the feature is requested for v8.5.7.What is the related PR or file link(s)?
Do your changes match any of the following descriptions?
Which TiDB components does this PR affect?
How do you ensure that your changes are correct? (Required)
/home/lhy1024/pdand/home/lhy1024/tikvimplementation for fields, defaults, and version fallback behavior../scripts/markdownlint pd-control.md troubleshoot-hot-spot-issues.md grafana-pd-dashboard.md.git diff --check.