Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: ticdc同步失效
【TiDB Usage Environment】Production Environment
【TiDB Version】v4.0.12
【Encountered Problem】ticdc is not synchronizing data to the downstream
【Reproduction Path】
【Problem Phenomenon and Impact】
1. ticdc was set up together with the tidb cluster
2. It has been running normally for a year
3. Suddenly, data cannot be synchronized to the downstream MySQL, and restarting the task has no effect. Moreover, there is no abnormal information in ticdc
Moreover, the logs in the ticdc node only print the following content:
Tried recreating the changefeed task but it didn’t work, still not syncing properly. Checking the status, I found that the synchronization timestamp doesn’t change at all.
Can waiting longer allow us to see the task error? Is rebuilding the task the same as rebuilding with the same name?
Are there large transactions?
I didn’t see any errors, it just outputs “Temporary file remove”. The newly created file is not the same name either. It has been running for a day now, and still hasn’t moved.
It should be that I imported a table with more than 400,000 rows of data using Excel at that time, and then the CDC stopped. I suspect it is related to this issue.
After observing for a while, I saw an error in a downstream database.
Is there another program writing to the downstream MySQL? You can check what the deadlock statement in MySQL is by using show engine innodb status\G;.
Data from September 13th? Is the GC setting that large?
Transaction retry unsuccessful, deadlock conflict detected.
|
username: Hacker_92quIrMM
|
username: 
|
username: 
