Bug #75769 5.6 with GTID_MODE=X cant connect to 5.7.6 with GTID_MODE=X_PERMISSIVE
Submitted: 4 Feb 2015 16:56 Modified: 29 Apr 2015 14:53
Reporter: Jorge Jordao Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:5.6.23 OS:Any
Assigned to: CPU Architecture:Any

[4 Feb 2015 16:56] Jorge Jordao
Description:
After WL#7083,
- a 5.7.6 master with GTID_MODE=OFF_PERMISSIVE generates anonymous transactions that a 5.6 slave with GTID_MODE=OFF should be able to replicate
- a 5.7.6 master with GTID_MODE=ON_PERMISSIVE generates GTID-transactions that a 5.6 slave with GTID_MODE=ON should be able to replicate

This is however not possible, as the 5.6 slave will refuse to connect to such master with message
[ERROR] Slave I/O: The slave IO thread stops because the master has an unknown @@GLOBAL.GTID_MODE. Error_code: 1593

How to repeat:
Try to connect a 5.6 slave with GTID_MODE=X to a 5.7.6 slave with GTID_MODE=X_PERMISSIVE.
[29 Apr 2015 15:06] David Moss
Noted in the 5.6.25 changelog:
A slave running MySQL 5.6.24 or earlier could not connect to a master running MySQL 5.7.6 and later that had gtid_mode=OFF_PERMISSIVE or gtid_mode=ON_PERMISSIVE. The fix ensures that a slave running MySQL 5.6.25 and later can connect to such a master as long as the slave's gtid_mode is compatible. In other words, a slave running MySQL 5.6.25 and later which has gtid_mode=OFF can connect to a master running MySQL 5.7.6 and later which has gtid_mode=OFF_PERMISSIVE, and a slave running MySQL 5.6.25 and later which has gtid_mode=ON can connect to a master running MySQL 5.7.6 and later which has gtid_mode=ON_PERMISSIVE. Other combinations are incompatible.