-
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
dm: update dm-precheck.md #8409
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
dm/dm-precheck.md
Outdated
|
||
- 分表存在自增主键,且自增主键 column 类型不为 bigint | ||
- 分表存在自增主键,自增主键 column 类型为 bigint,但没有为其配置列值转换 | ||
+ 检查上游是否处于 [Online-DDL](/dm/feature-online-ddl.md) 过程中,即创建了 `ghost` 表,但还未执行 `rename` 的阶段。 |
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.
再补充下这个检查结果吧。如果上游出于 online ddl 中,将会怎样,用户应该如何做
@okJiang 这个文档改动是适用于 v5.4 以后的版本吗? |
是的,我之前标错了 |
Co-authored-by: sunzy <[email protected]>
all comment fixed. ptal again @sunzhaoyang |
dm/dm-precheck.md
Outdated
```yaml | ||
mydumpers: # dump 处理单元的运行配置参数 | ||
global: # 配置名称 | ||
threads: 4 # dump 处理单元从上游数据库实例导出数据和 check-task 访问上游的线程数量,默认值为 4 |
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.
threads: 4 # dump 处理单元从上游数据库实例导出数据和 check-task 访问上游的线程数量,默认值为 4 | |
threads: 4 # dump 处理单元从上游数据库实例导出数据和执行前置检查时访问上游的线程数量,默认值为 4,建议不要超过 64。 |
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.
这个 64 是我拍的,可能不是合理的值
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.
之前的 dumpThread 有设置过大而产生的 issue 和 oncall 么?我们应该在文档中标明这个参数的影响就好了,例如
该参数与上游的连接数有关,如果太大可能会加大上游的负载
Co-authored-by: Ehco <[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.
LGTM
dm/dm-precheck.md
Outdated
|
||
对于全量加增量数据迁移模式,除了通用检查项外,前置检查还将包含全量数据迁移模式(`task-mode: full`)相关的检查项,以及增量数据迁移模式(`task-mode: incremental`)相关的检查项。 | ||
|
||
## 检查配置 |
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.
标题不够明确,检查配置和前面检查项是什么关系?
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.
这个是 checker 本身的配置,用于配置 checker 自己的参数的,和前面的检查项没关系
Co-authored-by: shichun-0415 <[email protected]>
dm/dm-precheck.md
Outdated
|
||
+ 数据库配置 | ||
* 通用检查项 |
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.
跟“通用检查项”并列的是什么呢?如果没有,用 item list 不太合适。
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.
因为 CI 里要求使用统一的 code block style
Co-authored-by: shichun-0415 <[email protected]>
Co-authored-by: shichun-0415 <[email protected]>
Co-authored-by: shichun-0415 <[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.
LGTM
/remove-status LGT1 |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 45c1846
|
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?