Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Binlog ack start may greater than binlog ack end, causing SyncWin corruption in the scenario of a timeout-reconnection between slave and master #2665

Closed
cheniujh opened this issue May 21, 2024 · 0 comments
Labels
☢️ Bug Something isn't working

Comments

@cheniujh
Copy link
Collaborator

cheniujh commented May 21, 2024

Is this a regression?

No

Description

Binlog ack start may greater than binlog ack end, causing SyncWin corruption in the scenario of a timeout-reconnection between slave and master. This Issue only occur in multi-DB scenario.
image
在主从超时场景下, 可能出现同步窗口崩溃的情况,具体特征是BinlogAckEnd小于BinlogAckStart。另外,这一case只出现在多DB情况下,单DB情况下未复现。

Please provide a link to a minimal reproduction of the bug

No response

Screenshots or videos

No response

Please provide the version you discovered this bug in (check about page for version information)

No response

Anything else?

No response

@cheniujh cheniujh added the ☢️ Bug Something isn't working label May 21, 2024
@cheniujh cheniujh changed the title Binlog ack end may greater than binlog ack start, causing SyncWin corruption in the scenario of a timeout-reconnection between slave and master Binlog ack start may greater than binlog ack end, causing SyncWin corruption in the scenario of a timeout-reconnection between slave and master May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
☢️ Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant