Bug #79272 | MySQl 5.5 master fails to replicate to MySQL 5.7.9 | ||
---|---|---|---|
Submitted: | 13 Nov 2015 14:08 | Modified: | 13 Nov 2015 14:30 |
Reporter: | Muhammad Irfan | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | OS: | Linux | |
Assigned to: | CPU Architecture: | Any |
[13 Nov 2015 14:08]
Muhammad Irfan
[13 Nov 2015 14:30]
MySQL Verification Team
Thank you for the bug report. behavior expected according documented. https://dev.mysql.com/doc/refman/5.7/en/replication-compatibility.html " MySQL supports replication from one release series to the next higher release series. For example, you can replicate from a master running MySQL 5.5 to a slave running MySQL 5.6, from a master running MySQL 5.6 to a slave running MySQL 5.7, and so on. However, you may encounter difficulties when replicating from an older master to a newer slave ...." https://dev.mysql.com/doc/refman/5.7/en/replication-options.html "When using MySQL replication, masters and slaves know each other's UUIDs. The value of a slave's UUID can be seen in the output of SHOW SLAVE HOSTS. Once START SLAVE has been executed, the value of the master's UUID is available on the slave in the output of SHOW SLAVE STATUS. " Last_IO_Error: Fatal error: The slave I/O thread stops because a fatal error is encountered when it tries to get the value of SERVER_UUID variable from master.
[26 May 2016 14:23]
IGG t
Are we likely to get a fix for this BUG (disable looking for master_UUID or similar), as until I am able to install and adequately test a 5.7 slave I'm unable to upgrade from my current 5.5 databases.
[17 Oct 2016 14:59]
Przemyslaw Malkowski
Seems that this one was already fixed in https://bugs.mysql.com/bug.php?id=80962 ...