Sync_diff

Translated
1

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

Original topic: sync_diff

| username: 胡杨树旁

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachment: Screenshot / Log / Monitoring]
Error reported when using sync_diff_inspector for data validation

[root@tidb02 bin]# ./sync_diff_inspector --config=config.toml  
A total of 1 tables need to be compared

Comparing the table structure of ``epp`.`insurance_area_face_mode`` ... failure
_____________________________________________________________________________
Progress [============================================================>] 100% 0/0
The structure of `epp`.`insurance_area_face_mode` is not equal, and data-check is skipped

The rest of tables are all equal.
The patch file has been generated in 
    'output/fix-on-tidb0/'
You can view the comparison details through './output/sync_diff.log'
2
| username: 胡杨树旁 | Original post link

To add: The table structure validation in the configuration file is set to false, but the table structure is still being validated during data validation.

3
| username: WalterWj | Original post link

How about trying a newer version of sync diff?

4
| username: 胡杨树旁 | Original post link

Found the cause. It is suspected that the table structure can be detected as unknown, but the SQL to repair the table structure cannot be output. Later, after modifying the table structure to be consistent, the SQL to repair the table structure can be output when executed again.

5
| username: system | Original post link

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