By checking the synchronization progress, you can learn about the progress of data synchronization. Synchronization tasks run in the following order: struct synchronization > full data synchronization > incremental data synchronization.
If the running status is Synchronizing struct, the system performs struct synchronization. In this case, check the progress bar of struct synchronization.
When the progress bar reaches 100%, the system completes this step.
If the running status is Full data sync started, the system performs full data synchronization. In this case, check the progress bar of full data synchronization.
When the progress bar reaches 100%, the system completes this step.
If the running status is Incremental data sync started, the system performs incremental data synchronization. In this case, check the latency of incremental data synchronization.
Procedure
On the Instance List page in the Data Sync module, select the corresponding instance, and click the instance ID to go to the Instance Management page.
On the Instance Management page, view the instance status and the synchronization progress.
Instructions on the Latency of Incremental Data Synchronization
Formula for calculating the latency: Latency = Current time on the source instance - Time of the latest record for successful synchronization to the destination instance in the incremental data log of the source instance. The unit is seconds.
No latency: The offset for completing synchronization through DTS is the same as the latest offset in the source database. All the incremental data generated in the source database is already synchronized to the destination database.
Latency-1 ms: After the task is started, no DDL or DML operations are performed on the tables synchronized in this task.
Not running: The task does not proceed to the incremental data synchronization phase, or the task is paused.
Note:
The calculation of the latency depends on the incremental data log of the source database. Therefore, when no DDL or DML operations are performed on the source database for a long time, the latency gradually increases and cannot accurately represent the actual synchronization latency. To obtain the actual latency, you can run SQL statements on the source database to refresh the metric.