The dm-worker dump data is stored under the deploy_dir by default

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: dm-worker dump数据默认存在了deploy_dir下面

| username: jaybing926

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Problem Phenomenon and Impact]
dm task-mode: full, full data import. The dump data is by default stored under deploy_dir, and data_dir is empty.
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

| username: Billmay表妹 | Original post link

When DM performs a full data migration, it exports the data from the source database to local files using the mysqldump tool. These files are stored by default in the dump subdirectory under the deploy_dir directory of the DM-worker. After the full data import is completed, DM will load these local files into the target database and clean up the files in the dump subdirectory under the deploy_dir directory. Therefore, after the full data import is completed, there should be data in the data_dir directory of the DM-worker.

If you find that there is no data in the data_dir directory, it may be due to the following reasons:

  1. The data_dir directory configuration of the DM-worker is incorrect, causing the data not to be correctly loaded into the target database. You can check whether the data-dir configuration item in the DM-worker’s configuration file is correct.
  2. An error occurred while the DM-worker was loading the data, causing the data not to be correctly loaded into the target database. You can check the DM-worker’s log files to understand the specific error information.

If the above methods do not solve your problem, it is recommended that you provide more information so that we can better help you resolve the issue.

| username: jaybing926 | Original post link

Does the display information in my screenshot indicate that the data dir I configured is correct? When performing a full data import, the data dir remains empty throughout.

| username: jansu-dev | Original post link

You can specify the dump directory in the task configuration. By default, it is a relative path, so it is under deploy. This issue has been raised by customers: “We hope that during the dump phase, data is written to the data_dir directory under the default or relative path” to standardize the use of product directories and avoid misunderstandings. The official team is currently evaluating this, but since it is a non-critical issue, it is undecided whether it will be fixed and when it will be fixed.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.