tidb dm导入数据报错 get binlog event error: ERROR 1236 (HY000)

【 TiDB 使用环境】测试
【 TiDB 版本】
【复现路径】做过哪些操作出现的问题
【遇到的问题:问题现象及影响】
【资源配置】进入到 TiDB Dashboard -集群信息 (Cluster Info) -主机(Hosts) 截图此页面
【附件:截图/日志/监控】
root@mongra ~]# tiup dmctl --master-addr 10.1.1.134:8261 query-status test
Starting component dmctl: /root/.tiup/components/dmctl/v8.1.0/dmctl/dmctl --master-addr 10.1.1.134:8261 query-status test
{
“result”: true,
“msg”: “”,
“sources”: [
{
“result”: true,
“msg”: “”,
“sourceStatus”: {
“source”: “mysql-css3”,
“worker”: “dm-10.1.1.136-8262”,
“result”: null,
“relayStatus”: null
},
“subTaskStatus”: [
{
“name”: “test”,
“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): Cannot replicate because the master purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new slave from backup. Consider increasing the master’s binary log expiration period. The GTID set sent by the slave is ‘836803d8-3a8c-11ee-8bfe-fa163e52bc6f:1-971261665:971261667-971261672’, and the missing transactions are ‘836803d8-3a8c-11ee-8bfe-fa163e52bc6f:971261666:971261673-971683243’”,
“RawCause”: “”,
“Workaround”: “Please check if the binlog file could be parsed by mysqlbinlog.”
}
],
“detail”: null
},
“unresolvedDDLLockID”: “”,
“sync”: {
“totalEvents”: “13”,
“totalTps”: “0”,
“recentTps”: “0”,
“masterBinlog”: “(mysql-bin.015111, 47227284)”,
“masterBinlogGtid”: “836803d8-3a8c-11ee-8bfe-fa163e52bc6f:1-975689962”,
“syncerBinlog”: “(mysql-bin.015028, 15339965)”,
“syncerBinlogGtid”: “836803d8-3a8c-11ee-8bfe-fa163e52bc6f:1-971261665:971261667-971261672”,
“blockingDDLs”: [
],
“unresolvedGroups”: [
],
“synced”: false,
“binlogType”: “remote”,
“secondsBehindMaster”: “0”,
“blockDDLOwner”: “”,
“conflictMsg”: “”,
“totalRows”: “13”,
“totalRps”: “0”,
“recentRps”: “0”
},
“validation”: null
}
]
}
]
}

上游 binlog 已经被清理了吧,还没同步到就被清理了

the master purged required binary logs.