Issues with Dumpling Backup and Restore, and Setting Up TiDB Replication to MySQL via TiCDC

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

Original topic: dumpling备份恢复,搭建tidb通过ticdc复制到mysql失败的问题

| username: 路在何chu

[TiDB Usage Environment] Production Environment

[TiDB Version]

[Reproduction Path] What operations were performed when the issue occurred
Performed a full backup of TiDB using dumpling, then restored it to MySQL. The restoration took about 35 hours. During the restoration, around the 24-hour mark, the tikv_gc_life_time was adjusted to 48 hours, and the ticdc gc-ttl was also adjusted to 48 hours. However, the task creation still reported an error:

| username: 路在何chu | Original post link

Later, by querying the TSO 444519644827746419, it corresponds to a time 24 hours ago, and 444498506308386858 corresponds to the moment when the backup was completed. It is suspected that the adjusted gc-ttl did not take effect. A bug was also found in the meantime, not sure if it is related to this issue TiDB 4.0.14 Release Notes | PingCAP Documentation Center

| username: 路在何chu | Original post link

The image is not visible. Please provide the text you need translated.

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

You should adjust the tikv_gc_life_time of TiDB before backup and recovery. After 35 hours of recovery, the GC should have already removed the data from 35 hours ago.

| username: 普罗米修斯 | Original post link

Before performing a full backup after an incremental backup, the GC time should be extended.

| username: Fly-bird | Original post link

Modify GC time

| username: 路在何chu | Original post link

Well, I have already made adjustments, backed up again, and restored. It has now been over 24 hours since the restoration. Should we wait and see if the issue persists?

| username: ajin0514 | Original post link

Try again.

| username: 路在何chu | Original post link

It is estimated to be a BUG. Before the backup, the gc-ttl of ticdc was adjusted to 48 hours, and tikv_gc_life_time was also adjusted to 48 hours. Then, after re-backing up, the same error was reported, so the recovery time can only be controlled within 24 hours.

| username: 路在何chu | Original post link

No matter how you adjust it, the expiration time of ticdc is 24 hours. It is estimated to be a bug in the lower version.

| username: system | Original post link

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