| title | Stop a Data Migration Task |
|---|---|
| summary | Learn how to stop a data migration task. |
You can use the stop-task command to stop a data migration task. For differences between stop-task and pause-task, refer to Pause a Data Migration Task.
{{< copyable "" >}}
help stop-taskstop a specified task
Usage:
dmctl stop-task [-s source ...] <task-name | task-file> [flags]
Flags:
-h, --help help for stop-task
Global Flags:
-s, --source strings MySQL Source ID
{{< copyable "" >}}
stop-task [-s "mysql-replica-01"] task-name-s: (Optional) Specifies the MySQL source where the subtasks of the migration task (that you want to stop) run. If it is set, only subtasks on the specified MySQL source are stopped.task-name | task-file: (Required) Specifies the task name or task file path.
{{< copyable "" >}}
stop-task test{
"op": "Stop",
"result": true,
"msg": "",
"sources": [
{
"result": true,
"msg": "",
"source": "mysql-replica-01",
"worker": "worker1"
}
]
}
Note:
After you stop a migration task with the
stop-taskcommand, runningquery-statuswill no longer display the task. However, the checkpoint and other related information for this task is still retained in thedm_metadatabase.
- To start over the migration task, add the
--remove-metaoption when running thestart-taskcommand.- To completely remove the migration task, manually delete the four tables that use the task name as a prefix from the
dm_metadatabase.