Overview
After a sync task is started, if it is interrupted due to an exception, you can manually retry it.
Full stage: The chunk-based import/export mechanism is implemented in this stage.Each chunk is assigned a unique identifier. With these identifiers, DTS can identify the unsynced chunk and resume the data sync from there when a disrupted task is restarted.
Incremental stage: The checkpoint-based mechanism is implemented in this stage. When DTS parses the source database binlogs before writing them to the target database, a checkpoint message is inserted to indicate the offset of the data being synced every 10 seconds. With these checkpoint messages, DTS can resume the data sync from the checkpointed offset when a disrupted task is restarted.
Below describes the scenarios where the task retry is supported for data sync:
Full export: Retry is only supported for exporting unlocked tables with primary keys. It doesn't work when exporting locked tables.
Full import: Retry is supported.
Incremental sync: Retry is supported.
Application Scope
Retry is supported data sync links among MySQL, TDSQL-C or MySQL, MariaDB, Percona, and Kafka.
Directions
Log in to the DTS console, select Data Sync on the left sidebar, select the target sync task, and click More > Retry in the Operation column.