-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
store limit v2: add more experimental description #19131
Conversation
configure-store-limit.md
Outdated
在该模式下,TiKV 执行速度成为迁移进度的主要瓶颈。你可以通过 **TiKV Details** > **Snapshot** > **Snapshot Speed** 面板判断当前调度速度是否达到 TiKV 限流设置。通过调整 TiKV Snapshot Limit ([`snap-io-max-bytes-per-sec`](/tikv-configuration-file.md#snap-io-max-bytes-per-sec)) 来增加或减少该节点的调度速度。 | ||
|
||
在当前版本中,将该配置项设置为 `"v2"` 为实验特性,不建议在生产环境中使用。 |
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.
from
docs-cn/pd-configuration-file.md
Line 430 in 148b399
> 在当前版本中,将该配置项设置为 `"v2"` 为实验特性,不建议在生产环境中使用。 |
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.
This feature is experimental between 7.1 and 8.5, and will GA in 8.5
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.
This feature is experimental between 7.1 and 8.5, and will GA in 8.5
@lhy1024 I recommend:
- Changing the base of this PR to
release-8.4
orrelease-7.1
. I will cherry-pick this PR to v7.1 and later versions. - Creating a new PR to upadte the
master
branch for v8.5 changes: removing the experimental note inLine 457 in 3c0975e
- `store-limit-version` 用于设置 `store limit` 限制模式,目前提供两种方式:`v1` 和 `v2`。默认值为 `v1`。在 `v1` 模式下,你可以手动修改 `store limit` 以限制单个 TiKV 调度速度。`v2` 模式为实验特性,不建议在生产环境中使用。在 `v2` 模式下,你无需关注 `store limit` 值,PD 将根据 TiKV Snapshot 执行情况动态调整 TiKV 调度速度。详情请参考 [Store Limit v2 原理](/configure-store-limit.md#store-limit-v2-原理)。
releases/release-7.1.0.md
Outdated
@@ -386,7 +386,7 @@ TiDB 7.1.0 为长期支持版本 (Long-Term Support Release, LTS)。 | |||
|
|||
+ PD | |||
|
|||
- 新增基于 snapshot 执行细节来自动调整 store limit 大小的控制器。将 `store-limit-version` 设置为 `v2` 即可开启该控制器,开启后,用户无需手动调整 `store limit` 配置来控制扩缩容的速度 [#6147](https://github.com/tikv/pd/issues/6147) @[bufferflies](https://github.com/bufferflies) | |||
- 新增基于 snapshot 执行细节来自动调整 store limit 大小的控制器(实验特性)。将 `store-limit-version` 设置为 `v2` 即可开启该控制器,开启后,用户无需手动调整 `store limit` 配置来控制扩缩容的速度 [#6147](https://github.com/tikv/pd/issues/6147) @[bufferflies](https://github.com/bufferflies) |
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.
@Oreoxmt PTAL
Signed-off-by: lhy1024 <[email protected]>
35511e3
to
4de6bb9
Compare
@niubell: 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-sigs/prow repository. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Oreoxmt 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 |
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 |
In response to a cherrypick label: new pull request created to branch |
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?