Has anyone found a way yet of circumventing MySQL 5.7s insistence that it's Master must have a server_UUID.
I currently have multiple instances of MySQL 5.5 over various sites, and want to look at upgrading to MySQL 5.7.
To do this I was planning to set up a test-site using some MySQL 5.7 databases running as a set of master > slaves from my main site.
But this failed at the first hurdle, as MySQL 5.7 insists that the Master must have a SERVER_UUID !! Depsite the official documentation telling us we should upgrade our slave databases before we upgrade the master.
In other words, when upgrading to MySQL 5.7, the slaves must be MySQL
5.7 before you can upgrade the master to 5.7.
http://dev.mysql.com/doc/refman/5.7/en/replication-upgrade.html
As it stands the only option appears to be to install, configure, and test a copy of MySQL 5.6 (which I'll never actually use) to act as an itermediary between my live system and test system. But that just introduces a whole load of additional complexity when trying to run like for like testing between 5.5. and 5.7 slaves (e.g. is it MySQL 5.7 that caused problem X, or was it MySQL 5.6 doing something on the way through etc).
I see that there is a BUG report for this, which they have since decided is Not actually a BUG, but a feature!!!
Best Answer
The problem is that MySQL 5.5 does not support GTIDs, but MySQL 5.7 does and have it activated by default.
As the MySQL manual suggests, you can disable GTIDs on the 5.7 slaves to perform your tests, and later, when all your servers will be upgraded to 5.7, activate GTIDs on both master and slaves.
see http://dev.mysql.com/doc/refman/5.7/en/replication-upgrade.html for more information.