MySQL Bugs: #80929: Master crashes when UUID is changed on slave and slave attempts to reconnect

Bug #80929	Master crashes when UUID is changed on slave and slave attempts to reconnect
Submitted:	1 Apr 2016 11:33	Modified:	6 Apr 2016 14:41
Reporter:	Cbg-Ops Patrick	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.6.15	OS:	CentOS
Assigned to:		CPU Architecture:	Any
Tags:	GTID, replication, UUID

Description:
I'm encountering an issue on a system running MySQL 5.6.15

GTID is enabled

Slave has got out of sync with it's master

Slave has a higher GTID executed value than the master is currently at so nothing is being replicated to the slave until the GTID value of the master reaches that of what it expects.

Manually, forcibly incrementing the gtid on the master with spurious inserts into a dummy table didn't work, resulting in a crash on the master when the slave attempted to connect

Changing the UUID on the slave so the master saw it as a 'new' slave caused the master to crash

This crash has been consistent based on topology and configuration but doesn't always happen at the point of slave connect so I'm unable to pinpoint the exact cause.

How to repeat:
Change UUID on slave and reconnect to master

output from mysqld.log

Attachment: logdump (application/octet-stream, text), 9.17 KiB.

Hello Patrick,

Thank you for the report.
This bug looks most likely duplicate of Bug #72085
Documented fix as follows in the 5.5.39, 5.6.20, and 5.7.5 changelogs:

    When using row-based replication, updating or deleting a row on
    the master that did not exist on the slave led to failure of the
    slave when it tried to process the change. This problem occurred
    with InnoDB tables lacking a primary key.

Please upgrade to the latest GA release and let us know if you are still having this issue along with exact reproducible test case.

Thanks,
Umesh

Get the error:
You do not have access to bug #72085.

when trying to view the duplicate

Upgrade path is in the pipeline but wanted to try and resolve some other issues in the short term