DM Synchronization MySQL Data Warning

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

Original topic: DM同步mysql数据警告

| username: lanranguidao

[TiDB Usage Environment] Testing/
[TiDB Version] v7.5.0
[Reproduction Path] What operations were performed to encounter the issue
Normal task configuration, then start the DM task, with MySQL 5.7 configured upstream.
[Encountered Issue: Problem Phenomenon and Impact]
The DM worker logs keep printing, with dozens of logs per second, but my data can be synchronized to MySQL normally.
[2023/12/28 10:12:03.445 +08:00] [WARN] [syncer.go:2445] [“unhandled event”] [task=task-test] [unit=“binlog replication”] [type=*replication.TableMapEvent]
[2023/12/28 10:12:03.447 +08:00] [WARN] [syncer.go:2445] [“unhandled event”] [task=task-test] [unit=“binlog replication”] [type=*replication.TableMapEvent]
[2023/12/28 10:12:03.447 +08:00] [WARN] [syncer.go:2445] [“unhandled event”] [task=task-test] [unit=“binlog replication”] [type=*replication.TableMapEvent]
[2023/12/28 10:12:03.447 +08:00] [WARN] [syncer.go:2445] [“unhandled event”] [task=task-test] [unit=“binlog replication”] [type=*replication.TableMapEvent]
[2023/12/28 10:12:03.448 +08:00] [WARN] [syncer.go:2445] [“unhandled event”] [task=task-test] [unit=“binlog replication”] [type=*replication.TableMapEvent]
[2023/12/28 10:12:03.448 +08:00] [WARN] [syncer.go:2445] [“unhandled event”] [task=task-test] [unit=“binlog replication”] [type=*replication.TableMapEvent]
[2023/12/28 10:12:03.448 +08:00] [WARN] [syncer.go:2445] [“unhandled event”] [task=task-test] [unit=“binlog replication”] [type=*replication.TableMapEvent]

[Resource Configuration] Enter TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page

[Attachments: Screenshots/Logs/Monitoring]

| username: wangccsy | Original post link

Warning errors are not a big issue?

| username: lanranguidao | Original post link

I didn’t see any impact on normal synchronization, it’s just flooding the logs.

| username: 有猫万事足 | Original post link

There are no other impacts, it’s just that the log level of two events is a bit high.

The bug was just fixed 3 weeks ago. The fix date is December 4th.
But the release date of DM version 7.5 is November 20th, so it does not include this fix.

Either increase the log level or wait for version 7.6 to come out and then upgrade.

| username: dba远航 | Original post link

No big deal.

| username: 烂番薯0 | Original post link

ware is not error

| username: 饭光小团 | Original post link

This is not a problem, it’s just encountering binlog events that cannot or do not need to be processed. You can increase the log level to make it quieter.

| username: 路在何chu | Original post link

This seems to be a BUG.