DM工具在同步过程中遇到panic error: table checkpoint position问题

【 TiDB 使用环境】生产环境
【 TiDB 版本】 V7.5.1
tiup dmctl --version
tiup is checking updates for component dmctl …
A new version of dmctl is available:
The latest version: v8.5.1
Local installed version: v8.0.0
Update current component: tiup update dmctl
Update all components: tiup update --all

【复现路径】
【遇到的问题】
DM同步数据,上游mysql5.7.25 , 未开启GTID,传统binlog pos方式同步 。在同步时出现如下错误:
“errors”: [
{
“ErrCode”: 36001,
“ErrClass”: “sync-unit”,
“ErrScope”: “internal”,
“ErrLevel”: “high”,
“Message”: “panic error: table checkpoint position: (mysql57-bin.002108, 20212127), gtid-set: 00000000-0000-0000-0000-000000000000:0 less than global checkpoint location(position: (mysql57-bin.002108, 31354389), gtid-set: 00000000-0000-0000-0000-000000000000:0) (flushed location(position: (mysql57-bin.002108, 31354389), gtid-set: 00000000-0000-0000-0000-000000000000:0))”,
“RawCause”: “”,
“Workaround”: “”
}
]
做的处置:
在论坛查询该错误先关内容,参考 DM报错 "ErrCode": 36001如何解决? - #3,来自 Hacker_7b2KWuuo 文章。进行了binlog文件核对,发现的确binlog文件超过了4G。 但是 现在的问题是 这个问题该如何解决,如何让同步进行下去。
【资源配置】
【复制黏贴 ERROR 报错的日志】
dm-worker.log (2.4 MB)

【其他附件:截图/日志/监控】

按照这个方案做了 现在还是有错误 ,具体如下
“result”: true,
“msg”: “”,
“sources”: [
{
“result”: true,
“msg”: “”,
“sourceStatus”: {
“source”: “mysql50133_3306”,
“worker”: “dm-192.168.55.25-8264”,
“result”: null,
“relayStatus”: {
“masterBinlog”: “(mysql57-bin.002172, 243054667)”,
“masterBinlogGtid”: “”,
“relaySubDir”: “75f42d7f-d854-11ed-bda4-286ed4897b05.000001”,
“relayBinlog”: “(mysql57-bin.002130, 188808650)”,
“relayBinlogGtid”: “”,
“relayCatchUpMaster”: false,
“stage”: “Running”,
“result”: null
}
},
“subTaskStatus”: [
{
“name”: “jz33062025”,
“stage”: “Paused”,
“unit”: “Sync”,
“result”: {
“isCanceled”: false,
“errors”: [
{
“ErrCode”: 36001,
“ErrClass”: “sync-unit”,
“ErrScope”: “internal”,
“ErrLevel”: “high”,
“Message”: “panic error: table checkpoint position: (mysql57-bin|000001.002108, 20212127), gtid-set: 00000000-0000-0000-0000-000000000000:0 less than global checkpoint location(position: (mysql57-bin|000001.002108, 31354389), gtid-set: 00000000-0000-0000-0000-000000000000:0) (flushed location(position: (mysql57-bin|000001.002108, 31354389), gtid-set: 00000000-0000-0000-0000-000000000000:0))”,
“RawCause”: “”,
“Workaround”: “”
}
],
“detail”: null
},
“unresolvedDDLLockID”: “”,
“sync”: {
“totalEvents”: “37707”,
“totalTps”: “179”,
“recentTps”: “0”,
“masterBinlog”: “(mysql57-bin.002172, 243054667)”,
“masterBinlogGtid”: “”,
“syncerBinlog”: “(mysql57-bin|000001.002108, 31354389)”,
“syncerBinlogGtid”: “00000000-0000-0000-0000-000000000000:0”,
“blockingDDLs”: [
],
“unresolvedGroups”: [
],
“synced”: false,
“binlogType”: “local”,
“secondsBehindMaster”: “412050”,
“blockDDLOwner”: “”,
“conflictMsg”: “”,
“totalRows”: “37707”,
“totalRps”: “179”,
“recentRps”: “0”
},
“validation”: null
}
]
}
]
下面是 relay log 目录


下面是更新 数据库 位置信息

有一个疑问的是 我更新的值为 mysql57-bin.002108 ,启动任务后 变为 mysql57-bin|000001.002108