When DM synchronizes DDL, secondsBehindMaster is 0

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: DM同步DDL时，secondsBehindMaster为0

| username: liujia

[TiDB Usage Environment] Production Environment
[TiDB Version] 5.3.0
[Reproduction Path] DM synchronizes a large table from MySQL to TiDB. After executing DDL on MySQL, check the status of DM, and secondsBehindMaster is 0.

[Attachment: Screenshot/Log/Monitoring]

Enterprise WeChat Screenshot_e4b01951-b7e2-487a-b536-cff343869915
Enterprise WeChat Screenshot_e4b01951-b7e2-487a-b536-cff343869915974×1000 69.6 KB

2
| username: 这里介绍不了我 | Original post link

It seems like it hasn’t caught up, but I see that your two GTIDs are consistent.

3
| username: liujia | Original post link

Inconsistent, look at the front.

4
| username: Lucien-卢西恩 | Original post link

Check if the downstream TiDB is currently executing DDL and investigate whether the DDL status is normal. DDL 语句的执行原理及最佳实践 | PingCAP 文档中心
Use DM troubleshooting methods to locate the current logs and monitoring situation.
TiDB Data Migration 性能问题及处理方法 | PingCAP 文档中心

5
| username: 小于同学 | Original post link

Check if there are any issues in the logs.