Data Transfer Service
- Release Notes and Announcements
- Announcements
- Product Introduction
- Specification Description
- Preparations
- Network Preparation
- Interworking Between local IDC and Tencent Cloud
- Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
- DTS Service Permission Preparation
- Data Migration
- Migration to MySQL Series
- Migrating to MySQL
- Migrating to MariaDB
- Migrating to TDSQL-C for MySQL
- Migrating to TDSQL MySQL
- Migrating to TDSQL TDStore
- Advanced Operations for MySQL Series Migration
- Processing for MySQL Series Pre-Check Failure
- Migrating to PostgreSQL
- Processing for PostgreSQL Series Pre-Check Failure
- Migrating to MongoDB
- Migration from MongoDB to MongoDB
- Fix for Verification Failure
- MongoDB Data Consistency Verification
- Migrating to SQL Server
- Migration from SQL Server to TencentDB for SQL Server
- Pre-Validation Failure Handling
- Migrating to TencentDB for Redis
- Migration from Redis to Redis
- Fix for Verification Failure
- Migrating to KeeWiDB
- Migration from Redis to KeeWiDB
- Task Management
- Data Sync
- Sync to MySQL series
- Sync to MySQL
- Sync to MariaDB
- Sync to TDSQL-C for MySQL
- Sync to TDSQL for MySQL
- Sync from TDSQL for MySQL to TDSQL for MySQL
- Sync to TDSQL TDStore
- MySQL Series Advanced Sync Operations
- MySQL series Pre Validation Failed Processing
- Synchronize to PostgreSQL
- PostgreSQL Pre Validation does not Pass Processing
- Synchronize to Kafka
- MySQL/MariaDB/Percona/TDSQL-C MySQL Sync to Kafka
- TDSQL MySQL Sync to Kafka
- Task Management
- Data Subscription (Kafka Edition)
- MySQL series Data Subscription
- Consuming MySQL Data
- Advanced Subscription Operations
- Fix for Verification Failure
- Data Subscription for TDSQL PostgreSQL
- Fix for Verification Failure
- MongoDB Data Subscription
- Fix for Verification Failure
- Task Management
- Consumption Management
- Fix for Verification Failure
- Monitoring and Alarms
- Configuring Metric Alarms and Event Alarms via the Console
- Practical Tutorial
- FAQs
- Error Handling
- API Documentation
- Making API Requests
- (NewDTS) Data Migration APIs
- Data Sync APIs
- Data Consistency Check APIs
- (NewDTS) Data Subscription APIs
- DTS API 2018-03-30
- Data Subscription APIs
- Making API Requests
- DTS APIs
- Service Agreement
Retrying Task (MySQL)
Last updated: 2024-07-08 19:09:49
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.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No