-
Notifications
You must be signed in to change notification settings - Fork 1.2k
pd: complement pd section #20500
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
pd: complement pd section #20500
Conversation
Signed-off-by: Ryan Leung <[email protected]>
@lhy1024: 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. |
@BornChanger: 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. |
/bot-review |
✅ AI review completed, 2 comments generated. |
dynamic-config.md
Outdated
| schedule.hot-regions-write-interval | 设置 PD 存储 Hot Region 信息时间间隔 | | ||
| schedule.hot-regions-reserved-days | 设置 PD 保留的 Hot Region 信息的最长时间 | | ||
| schedule.max-movable-hot-peer-size | 设置热点调度可以调度的最大 Region size | | ||
| schedule.store-limit-version | 设置 store limit 工作模式 | |
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.
| schedule.store-limit-version | 设置 store limit 工作模式 | | |
| schedule.store-limit-version | 设置 [store limit](/configure-store-limit.md) 工作模式 | |
dynamic-config.md
Outdated
| pd-server.use-region-storage | 开启独立的 Region 存储 | | ||
| pd-server.max-gap-reset-ts | 用于设置最大的重置 timestamp 的间隔(BR)| | ||
| pd-server.key-type| 用于设置集群 key 的类型 | | ||
| pd-server.metric-storage | 用于设置集群 metrics 的存储地址 | | ||
| pd-server.dashboard-address | 用于设置 dashboard 的地址 | | ||
| pd-server.flow-round-by-digit | PD 会对流量信息的末尾数字进行四舍五入处理,减少 Region 流量信息变化引起的统计信息更新 | |
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.
| pd-server.flow-round-by-digit | PD 会对流量信息的末尾数字进行四舍五入处理,减少 Region 流量信息变化引起的统计信息更新 | | |
| pd-server.flow-round-by-digit | 指定 PD 对 Region 流量信息的末尾数字进行四舍五入的位数 | |
dynamic-config.md
Outdated
| replication-mode.dr-auto-sync.primary-replicas | 是主 AZ 上 Voter 副本的数量 | | ||
| replication-mode.dr-auto-sync.dr-replicas | 是从 AZ 上 Voter 副本的数量 | |
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.
| replication-mode.dr-auto-sync.primary-replicas | 是主 AZ 上 Voter 副本的数量 | | |
| replication-mode.dr-auto-sync.dr-replicas | 是从 AZ 上 Voter 副本的数量 | | |
| replication-mode.dr-auto-sync.primary-replicas | 主 AZ 上 Voter 副本的数量 | | |
| replication-mode.dr-auto-sync.dr-replicas | 从 AZ 上 Voter 副本的数量 | |
dynamic-config.md
Outdated
| replication-mode.dr-auto-sync.wait-recover-timeout | 当网络恢复后,切换回 sync-recover 状态的等待时间 | | ||
| replication-mode.dr-auto-sync.pause-region-split | 用于控制在 async_wait 和 async 状态下是否暂停 Region 的 split 操作 | |
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.
| replication-mode.dr-auto-sync.wait-recover-timeout | 当网络恢复后,切换回 sync-recover 状态的等待时间 | | |
| replication-mode.dr-auto-sync.pause-region-split | 用于控制在 async_wait 和 async 状态下是否暂停 Region 的 split 操作 | | |
| replication-mode.dr-auto-sync.wait-recover-timeout | 当网络恢复后,切换回 `sync-recover` 状态的等待时间 | | |
| replication-mode.dr-auto-sync.pause-region-split | 用于控制在 `async_wait` 和 `async` 状态下是否暂停 Region 的 split 操作 | |
Signed-off-by: Ryan Leung <[email protected]>
Signed-off-by: Ryan Leung <[email protected]>
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.
Rest LGTM
pd-configuration-file.md
Outdated
@@ -307,6 +307,12 @@ pd-server 相关配置项。 | |||
+ 控制对同一个 Region 做 split 和 merge 操作的间隔,即对于新 split 的 Region 一段时间内不会被 merge。 | |||
+ 默认:1h | |||
|
|||
### `max-movable-hot-peer-size` |
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.
### `max-movable-hot-peer-size` | |
### `max-movable-hot-peer-size` <span class="version-mark">从 v7.1.0 版本开始引入</span> |
[LGTM Timeline notifier]Timeline:
|
Signed-off-by: Ryan Leung <[email protected]>
Signed-off-by: Ryan Leung <[email protected]>
Signed-off-by: Ryan Leung <[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 |
@qiancai: You cannot manually add or delete the cherry pick approval state labels, only I and the tursted members have permission to do so. You can approve it in internal platform. In response to removing label named approved. 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. |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
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?