backup: adjust concurrency description after v8.2 #20231
Conversation
|
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
missing-translation-status
ti-chi-bot
bot
added
size/S
|
@YuJuncen: 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. |
br/use-br-command-line-tool.md
Outdated
| @@ -57,7 +57,7 @@ tiup br backup full --pd "${PD_IP}:2379" \ | |||
| * `--cert`：指定 PEM 格式的 SSL 证书文件路径。 | |||
| * `--key`：指定 PEM 格式的 SSL 证书密钥文件路径。 | |||
| * `--status-addr`：向 Prometheus 提供统计数据的监听地址。 | |||
| * `--concurrency`：备份阶段的任务并发数。 | |||
| * `--concurrency`：控制备份阶段如何将任务拆分为多个请求，并以指定的并发数（concurrency）发送到同一个 TiKV 节点。该参数主要影响任务的拆分粒度，而不再直接决定备份的吞吐性能。通常无需修改默认值，如需提升备份性能，建议通过调整 tikv.backup.num-threads 参数来优化。 | |||
There was a problem hiding this comment.
事实上并不会影响拆分粒度吧，拆分粒度都是固定的 table / index 级别。
There was a problem hiding this comment.
表多的时候可能调大 concurrency 会带来比较大的速度改进？
There was a problem hiding this comment.
应该是请求的拆分粒度，而不是任务本身
hfxsd
added
translation/doing
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?