Linked Questions

Popular Questions

I am trying to add an instance to a cluster set with the mysqlsh command:

dba.get_cluster().add_instance("[email protected]:3306", {"ipAllowlist": "10.0.0.0/24"})

Then see the error

WARNING: Error in applier for group_replication_recovery: Worker 1 failed executing transaction '8873cb64-e90a-11ec-96fa-180373f152e2:10483' at source log binlog.004306, end_log_pos 278669;
Could not execute Write_rows event on table db_production.sessions;
Duplicate entry '63722726' for key 'sessions.PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's source log binlog.004306, end_log_pos 278669 (1062) at 2023-08-18 17:08:38.444870

I tried to delete the item in the table with delete from sessions where id = 63722726; but it doesn't make a difference.

I also attempted to look for duplicates using the mysqlbinlog utility:

mysqlbinlog --read-from-remote-server -h 10.0.0.90 -u cluster -p  binlog.004306  --verbose --base64-output=DECODE-ROWS | grep -A10 -B10  278669

However, I did not see anything that stood out, other than yes; there is a row with such id = 63722726.

This was originally caused by ubuntu unattended updates, updating the mysql version from 8.0.33 to 8.0.44 on one of the systems and that caused a version mismatch and break.

I'm not looking forward to what I think might be the fix, which is to edit the binary log by hand in a hex editor. :(

Has anyone seen this before, How can it be fixed?

Related Questions