BR: Add a new doc about creating table in batch #8659
Merged
Conversation
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
Co-authored-by: glorv <glorvs@163.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Conflicts: tidb-lightning/tidb-lightning-configuration.md
Contributor
Author
|
LGTM |
TomShawn
reviewed
Mar 25, 2022
en-jin19
reviewed
Mar 25, 2022
Co-authored-by: Enwei <jinenwei@pingcap.com>
Contributor
|
/merge |
Member
|
@en-jin19: DetailsIn 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 ti-community-infra/tichi repository. |
Contributor
|
/remove-status LGT1 |
ti-chi-bot
added
status/LGT2
Contributor
|
/merge |
Member
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: a26eb3e |
ti-chi-bot
added
the
status/can-merge
en-jin19
reviewed
Mar 29, 2022
|
|
||
| 使用 Backup & Restore (BR) 执行数据恢复任务时，BR 会先在下游 TiDB 集群创建库和表，再进行数据恢复。TiDB v6.0 之前，在数据恢复阶段创建表时，BR 采用了[串行执行](#实现原理)的方案。然而，当需要恢复的数据中带有大量的表（约 50000 张）时，该方案会在创建表上消耗较多时间。 | ||
|
|
||
| 为了通过加快创建表的速度和减少数据恢复的时间，从 TiDB v6.0 起，BR 引入了批量建表功能，此功能默认开启。 |
Contributor
There was a problem hiding this comment.
为了加快创建表的速度【，以】减少数据恢复的时间，【TiDB 在 v6.0.0 中引入了 BR 】批量建表功能，此功能默认开启。
en-jin19
reviewed
Mar 29, 2022
|
|
||
| # BR 批量建表 | ||
|
|
||
| 使用 Backup & Restore (BR) 执行数据恢复任务时，BR 会先在下游 TiDB 集群创建库和表，再进行数据恢复。TiDB v6.0 之前，在数据恢复阶段创建表时，BR 采用了[串行执行](#实现原理)的方案。然而，当需要恢复的数据中带有大量的表（约 50000 张）时，该方案会在创建表上消耗较多时间。 |
Contributor
There was a problem hiding this comment.
为了与第 39 行保持一致，第一句可修改为以下内容（确定所有修改内容后，会提 PR 进行修改）：
使用 Backup & Restore (BR) 执行数据恢复任务时，BR 会先在【目标 TiDB 集群上】创建库和表，再进行数据恢复。
en-jin19
reviewed
Mar 29, 2022
|
|
||
| ## 实现原理 | ||
|
|
||
| - v6.0 前的串行建表方案：在 v6.0 之前的版本，BR 采用了串行建表方案。在使用 BR 执行数据恢复任务时，BR 会先在目标 TiDB 创建库和表后，再开始进行数据恢复。建表时，BR 会在调用 TiDB 接口后，使用 SQL 语句 `Create Table` 创建表。建表任务由 TiDB DDL owner 依次串行执行。在每张表被创建时，各会引起一次 schema 版本的变更，而每次的 schema 版本的变更都需要同步到其他 BR 和其他 TiDB DDL worker。因此，当需要创建的表的数量比较多时，串行建表方案会导致建表时间过长。 |
Contributor
There was a problem hiding this comment.
- v6.0 前的串行建表方案：在 v6.0 之前的版本，BR 采用了串行建表方案。在使用 BR 执行数据恢复任务时，BR 会先在目标 TiDB 集群创建库和表后，再开始进行数据恢复。建表时，BR 会在调用 TiDB 内部接口后，使用 SQL 语句
Create Table创建表。建表任务由 TiDB DDL owner 依次串行执行。在每张表被创建时，各会引起一次 DDL schema 版本的变更，而每次的 schema 版本的变更都需要同步到其他 TiDB DDL worker（含 BR）。因此，当需要创建的表的数量比较多时，串行建表方案会导致建表时间过长。
en-jin19
added
translation/done
16 tasks
en-jin19
reviewed
Mar 30, 2022
| ## 实现原理 | ||
|
|
||
| - v6.0 前的串行建表方案：在 v6.0 之前的版本，BR 采用了串行建表方案。在使用 BR 执行数据恢复任务时，BR 会先在目标 TiDB 创建库和表后，再开始进行数据恢复。建表时，BR 会在调用 TiDB 接口后，使用 SQL 语句 `Create Table` 创建表。建表任务由 TiDB DDL owner 依次串行执行。在每张表被创建时，各会引起一次 schema 版本的变更，而每次的 schema 版本的变更都需要同步到其他 BR 和其他 TiDB DDL worker。因此，当需要创建的表的数量比较多时，串行建表方案会导致建表时间过长。 | ||
| - v6.0 起的批量建表方案：批量建表功能采用了并发批量建表方案。从 v6.0 起，在默认情况下，BR 会以 128 张表为一批，并发创建多批表。采用该方案后，BR 每建一批表时，TiDB schema 版本只会变更一次。此方法极大地提高了建表速度。 |
Contributor
There was a problem hiding this comment.
- v6.0 起的批量建表方案：从 v6.0 起，在默认情况下，BR 会以 128 张表为一批，并发创建多批表。采用该方案后，BR 每建一批表时，TiDB schema 版本只会变更一次。此方法极大地提高了建表速度。
15 tasks
This was referenced Apr 1, 2022
15 tasks
15 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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.
First-time contributors' checklist
What is changed, added or deleted? (Required)
Added a new document for introducing new features in BR. (br/br-freatures.md)
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?