TiDB's synchronization architecture through binlog frequently stops syncing

Translated
1

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

Original topic: TiDB 通过binlog 的同步架构经常停止同步

| username: ablewang_xiaobo

【TiDB Usage Environment】Production Environment
【TiDB Version】v4.0.9
【Encountered Problem】When synchronizing the TiDB database to another TiDB cluster, synchronization frequently stops. Both pump and drainer services are normal, and no errors are found in the logs.
【Reproduction Path】Restarting pump and drainer does not solve the problem
【Problem Phenomenon and Impact】

【Attachments】

image
image1380×368 33.4 KB

image
image1227×736 61.4 KB

2
| username: ablewang_xiaobo | Original post link

There have been two previous instances where synchronization stopped, with the situation being almost the same as above. Previously, the issue was resolved by reconstructing the synchronization, but it feels quite troublesome to do this every time.

3
| username: ablewang_xiaobo | Original post link

Currently, it cannot be determined that the above reason caused the synchronization to stop.

4
| username: cs58_dba | Original post link

Two TiDB clusters have different versions?

5
| username: ablewang_xiaobo | Original post link

The versions are the same.

6
| username: ablewang_xiaobo | Original post link

Found the reason, it was caused by some tables not having primary keys, which led to the interruption.

7
| username: cs58_dba | Original post link

The log message does indicate that.

8
| username: system | Original post link

This topic was automatically closed 1 minute after the last reply. No new replies are allowed.