DM任务报错handle a potential duplicate event

为提高效率,请提供以下信息,问题描述清晰能够更快得到解决:

【TiDB 版本】
v4.0.12
【DM 版本】
v1.0.6
【问题描述】

执行query-status single,提示报错
“msg”: “[code=30029:class=relay-unit:scope=internal:level=high] handle a potential duplicate event \u0026{Timestamp:1619102450 EventType:PreviousGTIDsEvent ServerID:2240880284 EventSize:71 LogPos:194 Flags:128} in mysql-bin.000148: check event \u0026{Timestamp:1619102450 EventType:PreviousGTIDsEvent ServerID:2240880284 EventSize:71 LogPos:194 Flags:128} whether duplicate in /dm/worker1/relay_log/d9c0cb84-86f4-11eb-b791-506b4b232bb0.000001/mysql-bin.000148: event from 123 in /dm/worker1/relay_log/d9c0cb84-86f4-11eb-b791-506b4b232bb0.000001/mysql-bin.000148 diff from passed-in event \u0026{Timestamp:1619102450 EventType:PreviousGTIDsEvent ServerID:2240880284 EventSize:71 LogPos:194 Flags:128}\ngithub.com/pingcap/dm/pkg/terror.(*Error).Generatef\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/pkg/terror/terror.go:237\ngithub.com/pingcap/dm/relay/writer.checkIsDuplicateEvent\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/relay/writer/file_util.go:157\ github.com/pingcap/dm/relay/writer.(*FileWriter).handleDuplicateEventsExist\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/relay/writer/file.go:369\ngithub.com/pingcap/dm/relay/writer.(*FileWriter).handlePotentialHoleOrDuplicate\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/relay/writer/file.go:312\ngithub.com/pingcap/dm/relay/writer.(*FileWriter).handleEventDefault\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/relay/writer/file.go:287\ngithub.com/pingcap/dm/relay/writer.(*FileWriter).WriteEvent\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/relay/writer/file.go:130\ngithub.com/pingcap/dm/relay.(*Relay).handleEvents\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/relay/relay.go:438\ngithub.com/pingcap/dm/relay.(*Relay).process\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/relay/relay.go:292\ngithub.com/pingcap/dm/relay.(*Relay).Process\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/relay/relay.go:191\ngithub.com/pingcap/dm/dm/worker.(*realRelayHolder).run\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/dm/worker/relay.go:167\ngithub.com/pingcap/dm/dm/worker.(*realRelayHolder).Start.func1\ \t/home/jenkins/agent/workspace/build_dm_master/go/src/github.com/pingcap/dm/dm/worker/relay.go:143\ runtime.goexit\ \t/usr/local/go/src/runtime/asm_amd64.s:1357”,

当前环境说明:
上游1个mysql实例,包含分库分表,和单表
下游tidb集群
dm worker 只有一个,用来同步上游分库分表和单表到下游tidb

先参考一下这个帖子,排查一下问题哈。