| 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: | |
| 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
[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.
[25 Mar 2022 12:13]
Prince Sachin
Last_IO_Errno: 1593
Last_IO_Error: The slave IO thread stops because the master has an unknown GTID_MODE.
Slave : mysql> select @@hostname, @@GTID_MODE,@@version;
+----------------+-------------+------------+
| @@hostname | @@GTID_MODE | @@version |
+----------------+-------------+------------+
| | OFF | 5.6.10-log |
+----------------+-------------+------------+
Master
mysql> select @@hostname, @@GTID_MODE,@@version;
+-----------------+----------------+------------+
| @@hostname | @@GTID_MODE | @@version |
+-----------------+----------------+------------+
| OFF_PERMISSIVE | 5.7.12-log |
+-----------------+----------------+------------+
1 row in set (0.51 sec)
