After resuming the data migration task, query the task to confirm whether it is normal. Why do you need to add resume-task after query-status?

Translated
1

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

Original topic: 数据迁移任务恢复后，在查询任务，确认任务是否正常，为什么query-status后面要添加上resume-task啊

| username: 希希希望啊

[TiDB Usage Environment] Production Environment
[TiDB Version] 7.5.1
[Reproduction Path] Refer to the official documentation 8.1 for migration scenarios with more columns downstream
[Encountered Problem: Problem Phenomenon and Impact] After the data migration task is restored, when querying the task to confirm whether the task is normal, why do you need to add resume-task after query-status resume-task ${task-name}?
[Attachment: Screenshot/Log/Monitoring]
Screenshot

Image
Image1380×830 163 KB

2
| username: 希希希望啊 | Original post link

Is there a teacher who can help take a look? I haven’t dared to execute it in the production environment yet.

3
| username: zhaokede | Original post link

This is a recovery task, right? No need to include resume-task;
tiup dmctl --master-addr= master-addr query-status task-name
The prefix of your command is query, not an operation command, so feel free to execute it.

4
| username: zhaokede | Original post link

Is this also your feedback?

5
| username: 我是吉米哥 | Original post link

Use the command line help to check the usage and verify.

6
| username: zhaokede | Original post link

The main reason is that the original poster saw it written this way in the documentation manual.