DM binary 方式部署 start-task 报错

【 TiDB 使用环境】生产环境 /测试/ Poc
【 TiDB 版本】
【复现路径】做过哪些操作出现的问题

{
“result”: true,
“msg”: “”,
“sources”: [
{
“result”: true,
“msg”: “”,
“sourceStatus”: {
“source”: “mysql-01”,
“worker”: “worker1”,
“result”: null,
“relayStatus”: null
},
“subTaskStatus”: [
{
“name”: “shard_merge”,
“stage”: “Paused”,
“unit”: “Sync”,
“result”: {
“isCanceled”: false,
“errors”: [
{
“ErrCode”: 36069,
“ErrClass”: “sync-unit”,
“ErrScope”: “upstream”,
“ErrLevel”: “high”,
“Message”: “get binlog event error: ERROR 1236 (HY000): Client requested master to start replication from position \u003e file size”,
“RawCause”: “”,
“Workaround”: “Please check if the binlog file could be parsed by mysqlbinlog.”
}
],
“detail”: null
},
“unresolvedDDLLockID”: “”,
“sync”: {
“totalEvents”: “7”,
“totalTps”: “0”,
“recentTps”: “0”,
“masterBinlog”: “(mybinlog.000004, 194)”,
“masterBinlogGtid”: “d6170ffa-c6fa-11ed-bd6d-46a07fb8ee2c:1-4”,
“syncerBinlog”: “(mybinlog.000003, 4753)”,
“syncerBinlogGtid”: “d6170ffa-c6fa-11ed-bd6d-46a07fb8ee2c:1-18”,
“blockingDDLs”: [
],
“unresolvedGroups”: [
],
“synced”: false,
“binlogType”: “remote”,
“secondsBehindMaster”: “0”,
“blockDDLOwner”: “”,
“conflictMsg”: “”,
“totalRows”: “7”,
“totalRps”: “0”,
“recentRps”: “0”
},
“validation”: null
}

【遇到的问题:问题现象及影响】
【资源配置】
【附件:截图/日志/监控】

上游的 binlog 是正常的么?

如果是主从切换过,推荐使用 gtid…

参考这个帖子:

找到原因了,我备库dm_meta库,之前测试的binlog元数据还在

此话题已在最后回复的 60 天后被自动关闭。不再允许新回复。