-
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
Merge DM dev docs to TiDB dev docs #8042
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-faq.md
Outdated
- TiDB Server 的全局变量 `max_allowed_packet` | ||
- 任务配置文件中的配置项 `target-database.max-allowed-packet`(详情参见 [DM 任务完整配置文件介绍](/dm/task-configuration-file-full.md)) | ||
|
||
设置为比默认 67108864 (64M) 更大的值。详见 [Loader 解决方案](https://docs.pingcap.com/zh/tidb/stable/loader-overview#解决方案)。 |
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.
Loader 在 v5.0 中就废弃了
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.
@sunzhaoyang 请帮忙看下是否有 Loader 的替代方案呢?谢谢
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.
这个 bug 在 dm v2.0 GA 版本就已经修复了。我觉得可以采用如下两个方案:
- 去掉这个链接,如果还有用老版本的用户遇到这个问题,直接告诉他需要怎么workaround 就够了,不用在强调 loader.
- 将链接强制跳转到 3.0/4.0 版本的 loader 配置页面,即 https://docs.pingcap.com/zh/tidb/v4.0/loader-overview/
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.
Done.
dm/dm-faq.md
Outdated
该情况有两种解决方案: | ||
|
||
- 如果数据量较小(TB 级以下)或任务有合库合表:清空下游数据库的已导入数据,同时清空导出数据目录,使用 dmctl 删除并 `start-task --remove-meta` 重建任务。后续尽量保证全量导出导入阶段 DM 没有冗余 worker 以及避免在该时段内重启或升级 DM 集群。 | ||
- 如果数据量较大(数 TB 或更多):清空下游数据库的已导入数据,将 lightning 部署到数据所在的 DM worker 节点,使用 [lightning local backend 模式](https://docs.pingcap.com/zh/tidb/dev/deploy-tidb-lightning) 导入 DM dump 单元导出的数据。全量导入完成后,修改任务的 `task-mode` 为 `incremental`,修改 `mysql-instance.meta.pos` 为 dump 单元导出数据 `metadata` 中记录的位置,启动一个增量任务。 |
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.
Global comment: Please check all links that start with https://docs.pingcap.com/zh/tidb/
and https://pingcap.com/docs-cn/
.
- 如果数据量较大(数 TB 或更多):清空下游数据库的已导入数据,将 lightning 部署到数据所在的 DM worker 节点,使用 [lightning local backend 模式](https://docs.pingcap.com/zh/tidb/dev/deploy-tidb-lightning) 导入 DM dump 单元导出的数据。全量导入完成后,修改任务的 `task-mode` 为 `incremental`,修改 `mysql-instance.meta.pos` 为 dump 单元导出数据 `metadata` 中记录的位置,启动一个增量任务。 | |
- 如果数据量较大(数 TB 或更多):清空下游数据库的已导入数据,将 lightning 部署到数据所在的 DM worker 节点,使用 [lightning local backend 模式](https://docs.pingcap.com/zh/tidb/dev/deploy-tidb-lightning) 导入 DM dump 单元导出的数据。全量导入完成后,修改任务的 `task-mode` 为 `incremental`,修改 `mysql-instance.meta.pos` 为 dump 单元导出数据 `metadata` 中记录的位置,启动一个增量任务。 |
dm/dm-precheck.md
Outdated
TiDB 和 MySQL 的兼容性存在以下一些区别: | ||
|
||
- TiDB 不支持外键 | ||
- 字符集的兼容性不同,详见 [TiDB 支持的字符集](https://pingcap.com/docs-cn/dev/reference/sql/character-set/) |
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.
ditto
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: a3d0fa6
|
What is changed, added or deleted? (Required)
To help users access TiDB Data Migration (DM) documentation more quickly and conveniently, this PR merges TiDB DM dev docs into TiDB dev docs.
The major changes are as follows:
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?