How to Achieve Delayed Replication Between TiDB Clusters

Translated
1

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

Original topic: tidb集群之间怎样实现延时复制

| username: TiDBer_OB4kHrS7

[TiDB Usage Environment] Production Environment
[TiDB Version] V5.3.3
[Encountered Problem: Problem Phenomenon and Impact]
How to achieve delayed replication between two TiDB clusters?

2
| username: WalterWj | Original post link

I think you need to go to the requirements section to submit your request.

3
| username: Kongdom | Original post link

Are you referring to this?

4
| username: 啦啦啦啦啦 | Original post link

TiCDC should not support delayed replication similar to MySQL master-slave. The purpose of delayed replication is generally for quick rollback, and with the GC mechanism, there should be no need to worry. You can increase the GC time for the disaster recovery cluster.

5
| username: TiDBer_OB4kHrS7 | Original post link

Neither drainer nor ticdc can achieve delayed replication.

6
| username: Kongdom | Original post link

Well, I misunderstood.

7
| username: xingzhenxiang | Original post link

Isn’t it a bit convoluted to go from TiDB to MySQL, then experience latency, and back to TiDB?

8
| username: TiDBer_OB4kHrS7 | Original post link

It’s a detour, there’s no MySQL in between, only TiDB-TiDB, and there won’t be an additional MySQL in between.