TiDB DM v6.3.0 Synchronization Task Stuck

Translated
1

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

Original topic: tidb DM v6.3.0同步任务卡住

| username: lemontree8801

[TiDB Usage Environment] Production Environment
[TiDB Version] v.6.1.2 DM Version v6.3.0
[Reproduction Path] Upstream sharded table performed tablespace reclamation ALTER TABLE fms_voucher_x.vc_fms_voucher_item_0 ENGINE = innodb. At that time, only one sharded table fms_voucher_0.vc_fms_voucher_item_0 was processed, causing the task to stall. Later, DDL tasks were processed on the upstream for fms_voucher_2.vc_fms_voucher_item_0, fms_voucher_1.vc_fms_voucher_item_0, fms_voucher_3.vc_fms_voucher_item_0. After pausing and resuming the DM synchronization task, the error shown in the image occurred after some time. I don’t want to perform DDL operations on the table again. Could you please advise on how to restore DM synchronization in this situation?
[Encountered Problem: Symptoms and Impact]
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

image
image1380×480 50.5 KB

2
| username: 特雷西-迈克-格雷迪 | Original post link

Scenario 1: binlog skip <task-name>, skip the current erroneous DDL statement.
Scenario 2: binlog replace <task-name> <replace-sql1> <replace-sql2>, replace the erroneous statement with equivalent SQL statements.
Reference: 使用 TiDB Data Migration 处理出错的 DDL 语句 | PingCAP 文档中心

3
| username: tidb菜鸟一只 | Original post link

In your case, can’t you just use binlog skip ? The table engine hasn’t changed, it’s just that the source executed alter table engine=innodb for downsizing, right? It doesn’t matter if the downstream doesn’t execute it.

4
| username: lemontree8801 | Original post link

Skipping is not possible, it directly prompts no error.

5
| username: lemontree8801 | Original post link

image
image1186×758 98 KB

6
| username: tidb菜鸟一只 | Original post link

Skip the binlog at the specified DDL operation position using -b.

7
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.