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
{{ message }}
This repository has been archived by the owner on Nov 5, 2022. It is now read-only.
Hello - I was trying to use slave parallel threads to replicate from the ripple server.
However, I hit the below issue after some time:
Last_SQL_Error: Cannot execute the current event group in the parallel mode. Encountered event Gtid, relay-log name /mysql_data/relaylogs/relay-log.000005, position 27023962 which prevents execution of this event group in parallel mode. Reason: The master event is logically timestamped incorrectly.
I tracked this down to a binlog rotation happening on the master and the sequence number getting reset to 1 and hence the parallel thread failure. Could you confirm if handling the rotate events is an issue and any workarounds ?
Thanks!
The text was updated successfully, but these errors were encountered:
Unfortunately I can't say how Ripple interacts with MySQL's rotations, logical timestamping and parallel replication. We've never tested that. I should probably investigate this question more closely...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello - I was trying to use slave parallel threads to replicate from the ripple server.
However, I hit the below issue after some time:
Last_SQL_Error: Cannot execute the current event group in the parallel mode. Encountered event Gtid, relay-log name /mysql_data/relaylogs/relay-log.000005, position 27023962 which prevents execution of this event group in parallel mode. Reason: The master event is logically timestamped incorrectly.
I tracked this down to a binlog rotation happening on the master and the sequence number getting reset to 1 and hence the parallel thread failure. Could you confirm if handling the rotate events is an issue and any workarounds ?
Thanks!
The text was updated successfully, but these errors were encountered: