The syncer task's target position is greater than the actual binlog position, Client requested master to start replication from position > file size

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: syncer任务的指向pos大于实际binlog pos，Client requested master to start replication from position > file size

| username: freywan

[TiDB Usage Environment] Production Environment
[TiDB Version] v5.2.3
[DM Version] v2.0.7
[Encountered Issue] The syncer task’s pos is greater than the actual binlog pos

image
image1328×806 16.2 KB

image
image465×613 10.6 KB

image

image
image1380×532 59.3 KB

image
image880×534 75.1 KB

[Reproduction Path] Attempted to re-fetch binlog before noticing the pos issue, but it couldn’t be resolved
[Issue Phenomenon and Impact] Currently, this data source is divided into two sources for sharding synchronization, affecting nearly 20 tasks, and production data synchronization has stopped
[Attachments]
Logs of the day when the master-slave desynchronization occurred and logs of 20220704
dm-worker.log.20220704.tar.gz (6.8 MB)
dm-worker.log.20220701.tar.gz (13.8 MB)

Additionally, the logs captured an EOF error located on the binlog where the error occurred:

%E4%BC%81%E4%B8%9A%E5%BE%AE%E4%BF%A1%E6%88%AA%E5%9B%BE_16569298231648
%E4%BC%81%E4%B8%9A%E5%BE%AE%E4%BF%A1%E6%88%AA%E5%9B%BE_165692982316481638×202 26.6 KB

2
| username: lance6716 | Original post link

Is your upstream RDS? The size of this binlog file has indeed decreased.

3
| username: freywan | Original post link

It’s RDS:rofl:

4
| username: lance6716 | Original post link

You can submit a ticket to them. May I ask which company it is? It would help us accumulate RDS experience.

For DM, you can try going back to an earlier position, enable safemode for synchronization, or redo from the full backup.

5
| username: system | Original post link

This topic was automatically closed 1 minute after the last reply. No new replies are allowed.