Error of Missing Tables Reported by DM Component During Synchronization

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

Original topic: dm组件同步报少表的错误

| username: Jjjjayson_zeng

【TiDB Usage Environment】Production Environment
【TiDB Version】
【Reproduction Path】Difficult to infer which operations were performed
【Encountered Issues: Problem Phenomenon and Impact】
【Resource Configuration】
【Attachments: Screenshots/Logs/Monitoring】

MySQL synchronization to TiDB

| username: Hacker_小峰 | Original post link

Does this table exist in both the upstream MySQL and downstream TiDB?
Did DM suddenly report an error and pause?

| username: Jjjjayson_zeng | Original post link

The upstream exists, but the downstream does not. The downstream does not know why it does not exist. Was it deleted by someone on the TiDB side, or was it deleted and recreated by MySQL?

| username: Hacker_小峰 | Original post link

Have you set up synchronization filtering rules? Is the non-existent table mentioned in the error message one that needs to be synchronized?
Is it similar to the situation encountered in this article: DM同步MYSQL报错 表不存在 xxx table does not exist - TiDB 的问答社区

| username: Jjjjayson_zeng | Original post link

Of course, it is needed. No need to put it on the blacklist.

| username: Hacker007 | Original post link

Occasionally, I also encounter this situation in the development environment. After manually creating the downstream table, just skip this error.

| username: Jjjjayson_zeng | Original post link

I’m the same, but with hundreds of tasks, I don’t have time to do anything else every day.

| username: Hacker007 | Original post link

You can check if these tables are also synchronized in other tasks, if so, you can ignore it.

| username: Jjjjayson_zeng | Original post link

This thing uses binlog, which means that each task will check the binlog once if it uses this table. However, this table happens to be used by all users, which is normal for over 200 users to use it. Each one checks it and then reports an error.

| username: dba-kit | Original post link

Please paste the task.yaml configuration file to see if there is an issue with the regular expression.

| username: Hacker007 | Original post link

Then you need to ignore this table in all tasks, leaving only one task. It requires some work, but it’s a one-time effort.

| username: liuis | Original post link

Ignore this table.