Docs Menu
Docs Home
/
Relational Migrator
/

Stop a Migration Job

On this page

  • About this Task
  • Steps
  • Learn More

You can stop a migration job from the Job Overview pane on the Data Migration tab.

This task also applies to Apache Kafka supported continuous migration jobs. There is no procedural difference introduced when using Kafka. For more details, see Integrating Relational Migrator with Kafka.

The effects of stopping a migration job on your destination database depend on the type and stage of the migration job:

  • If you stop a snapshot migration job during the snapshot stage, any partially migrated data remains in the MongoDB database.

  • If you stop a continuous migration job during the CDC stage, the process ends gracefully, and Relational Migrator cleans up any temporary data.

  • After a migration job is stopped, you cannot resume it. To migrate data from a stopped migration job, you can create a new job and select the option Drop destination collections before migration.

Once initiated, the process of canceling or completing a migration job may take up to one minute.

To stop your migration job, follow the instructions below based on the current stage of execution:

1
2
3
  1. Click the red Terminate button in the upper-right corner of the screen.

  2. Click the red Terminate button on the pop-up modal. Once a migration job cancels, an x icon displays in the History pane, and the status of the migration job updates to Snapshot cancelled.

1
2
3
  1. Click the Complete CDC button in the upper-right corner of the screen.

  2. Click the green Complete CDC button on the pop-up modal. Upon completion, the migration job displays a in the History pane and marks all stages as Completed. The status is updated to CDC Completed.

Back

Monitor