You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
在主从超时场景下, 可能出现同步窗口崩溃的情况,具体特征是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
The text was updated successfully, but these errors were encountered:
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
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.
在主从超时场景下, 可能出现同步窗口崩溃的情况,具体特征是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
The text was updated successfully, but these errors were encountered: