一个好的问题描述有利于社区小伙伴更快帮你定位到问题，高效解决你的问题
1.这是我遇到的错误，遇到tidb和mysql数量对不上的时候，直接就终止，个人感觉这个是个bug，我本身就是为了对比两边数据是否一致，要追平tidb的数据；
后续通过更改range参数，指定id的范围，可以解决该问题；
2.另外，当我不指定config的时候，表的对比降级很严重，不会走唯一索引的分片对比，这个是否可以考虑优化一下；
我的系统是ARM mysql是用的8+ tidb全家桶都是8.5.6
[2026/05/26 09:48:06.974 +08:00] [INFO] [diff.go:319] [“global consume chunk info”] [“chunk index”=“{"table-index":12,"bucket-index-left":0,"bucket-index-right":256,"chunk-index":0,"chunk-count":1}”] [“chunk bound”=“”]
[2026/05/26 09:48:08.067 +08:00] [INFO] [checkpoints.go:255] [“save checkpoint”] [chunk=“{"state":"failed","chunk-range":{"index":{"table-index":7,"bucket-index-left":0,"bucket-index-right":256,"chunk-index":0,"chunk-count":1},"type":1,"bounds":,"is-first":false,"is-last":false,"where":"((TRUE) AND (TRUE))","args":null,"index-column-names":[{"O":"id","L":"id"}]},"index-id":1}”] [state=failed]
[2026/05/26 09:48:15.709 +08:00] [FATAL] [diff.go:582] [“the count is not correct”] [count1=772741] [count2=772739] [count=1545478] [stack=“github.com/pingcap/tiflow/sync_diff_inspector/diff.(*Diff).binSearch\n\tgithub.com/pingcap/tiflow/sync_diff_inspector/diff/diff.go:582\ngithub.com/pingcap/tiflow/sync_diff_inspector/diff.(*Diff).BinGenerate\n\tgithub.com/pingcap/tiflow/sync_diff_inspector/diff/diff.go:539\ngithub.com/pingcap/tiflow/sync_diff_inspector/diff.(*Diff).consume\n\tgithub.com/pingcap/tiflow/sync_diff_inspector/diff/diff.go:478\ngithub.com/pingcap/tiflow/sync_diff_inspector/diff.(*Diff).Equal.func2\n\tgithub.com/pingcap/tiflow/sync_diff_inspector/diff/diff.go:321\ngithub.com/pingcap/tiflow/sync_diff_inspector/utils.(*WorkerPool).Apply.func1\n\tgithub.com/pingcap/tiflow/sync_diff_inspector/utils/utils.go:110”]
【TiDB 使用环境】生产环境 /测试环境
【TiDB 版本】
【部署方式】云上部署（什么云）/机器部署
【操作系统/CPU 架构/芯片详情】
【机器部署详情】CPU大小/内存大小/磁盘大小
【集群数据量】
【集群节点数】
【问题复现路径】做过哪些操作出现的问题
【遇到的问题：问题现象及影响】
【资源配置】进入到 TiDB Dashboard -集群信息 (Cluster Info) -主机(Hosts) 截图此页面
【复制黏贴 ERROR 报错的日志】
【其他附件：截图/日志/监控】
