Questions about Data Verification in TiCDC-based TiDB Primary-Secondary Cluster

Translated
1

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

Original topic: ticdc base TiDB主备集群数据校验 疑问贴

| username: TiDBer_yyy

[TiDB Version] 5.0.4
[Problem Encountered] Using TiCDC to synchronize data between TiDB primary and standby clusters, can the sync-diff-inspector tool be used to verify data consistency? How to configure the snapshot?

Data Verification of TiDB Primary and Standby Clusters will check and obtain the upstream and downstream timestamps.

select * from tidb_binlog.checkpoint;

Does TiCDC check the checkpoint-ts timestamp?

"status": {
    "resolved-ts": 419036036249681921,
    "checkpoint-ts": 419036036249681921,
    "admin-job-type": 0
  },
2
| username: neilshen | Original post link

Currently, TiCDC does not have such a feature. You can only stop upstream writes first, then ensure the checkpoint reaches the stop time before using sync-diff-inspector to check.

3
| username: 啦啦啦啦啦 | Original post link

TiCDC doesn’t work; you can set up a TiDB master-slave cluster using TiDB Binlog.

4
| username: TiDBer_yyy | Original post link

Thank you for the reply:
It seems that the official recommendation of binlog-based master-slave synchronization still has official considerations.

5
| username: system | Original post link

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