Data Check for TiDB Upstream and Downstream Clusters

You can use TiDB Binlog to build upstream and downstream clusters of TiDB. When Drainer replicates data to TiDB, the checkpoint is saved and the TSO mapping relationship between the upstream and downstream is also saved as ts-map. To check data between the upstream and downstream, configure snapshot in sync-diff-inspector.

Step 1: obtain ts-map

To obtain ts-map, execute the following SQL statement in the downstream TiDB cluster:

mysql> select * from tidb_binlog.checkpoint; +---------------------+---------------------------------------------------------------------------------------------------------+ | clusterID | checkPoint | +---------------------+---------------------------------------------------------------------------------------------------------+ | 6711243465327639221 | {"commitTS":409622383615541249,"ts-map":{"master-ts":409621863377928194,"slave-ts":409621863377928345}} | +---------------------+---------------------------------------------------------------------------------------------------------+

Step 2: configure snapshot

Then configure the snapshot information of the upstream and downstream databases by using the ts-map information obtained in Step 1.

Here is a configuration example of the Databases config section:

######################### Databases config ######################### # Configuration of the source database instance [[source-db]] host = "127.0.0.1" port = 4000 user = "root" password = "123456" # The instance ID of the source database, the unique identifier of a database instance instance-id = "source-1" # Uses the snapshot function of TiDB, corresponding to the master-ts in ts-map snapshot = "409621863377928194" # Configuration of the target database instance [target-db] host = "127.0.0.1" port = 4001 user = "root" password = "123456" # Uses the snapshot function of TiDB, corresponding to the slave-ts in ts-map snapshot = "409621863377928345"