When you upgrade servers that participate in a replication setup, the procedure for upgrading depends on the current server versions and the version to which you are upgrading. This section provides information about how upgrading affects replication. For general information about upgrading MySQL, see Section 2.11, “Upgrading MySQL”
When you upgrade a master to 5.7 from an earlier MySQL release series, you should first ensure that all the slaves of this master are using the same 5.7.x release. If this is not the case, you should first upgrade the slaves. To upgrade each slave, shut it down, upgrade it to the appropriate 5.7.x version, restart it, and restart replication. Relay logs created by the slave after the upgrade are in 5.7 format.
Changes affecting operations in strict SQL mode
STRICT_ALL_TABLES) may result in
replication failure on an updated slave. For example, as of MySQL
5.7.2, the server restricts insertion of a
DEFAULT value of 0 for temporal data types in
strict mode. If you use statement-based logging
binlog_format=STATEMENT), if a
slave is upgraded before the master, the nonupgraded master will
execute statements without error that may fail on the slave and
replication will stop. To deal with this, stop all new statements
on the master and wait until the slaves catch up. Then upgrade the
slaves. Alternatively, if you cannot stop new statements,
temporarily change to row-based logging on the master
binlog_format=ROW) and wait
until all slaves have processed all binary logs produced up to the
point of this change. Then upgrade the slaves.
After the slaves have been upgraded, shut down the master, upgrade it to the same 5.7.x release as the slaves, and restart it. If you had temporarily changed the master to row-based logging, change it back to statement-based logging. The 5.7 master is able to read the old binary logs written prior to the upgrade and to send them to the 5.7 slaves. The slaves recognize the old format and handle it properly. Binary logs created by the master subsequent to the upgrade are in 5.7 format. These too are recognized by the 5.7 slaves.
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. Note that downgrading from 5.7 to older versions does not work so simply: You must ensure that any 5.7 binary log or relay log has been fully processed, so that you can remove it before proceeding with the downgrade.
Some upgrades may require that you drop and re-create database objects when you move from one MySQL series to the next. For example, collation changes might require that table indexes be rebuilt. Such operations, if necessary, are detailed at Section 2.11.3, “Changes in MySQL 5.7”. It is safest to perform these operations separately on the slaves and the master, and to disable replication of these operations from the master to the slave. To achieve this, use the following procedure:
Stop all the slaves and upgrade them. Restart them with the
--skip-slave-startoption so that they do not connect to the master. Perform any table repair or rebuilding operations needed to re-create database objects, such as use of
ALTER TABLE, or dumping and reloading tables or triggers.
Disable the binary log on the master. To do this without restarting the master, execute a
SET sql_log_bin = OFFstatement. Alternatively, stop the master and restart it without the
--log-binoption. If you restart the master, you might also want to disallow client connections. For example, if all clients connect using TCP/IP, enable the
skip_networkingsystem variable when you restart the master.
With the binary log disabled, perform any table repair or rebuilding operations needed to re-create database objects. The binary log must be disabled during this step to prevent these operations from being logged and sent to the slaves later.
Re-enable the binary log on the master. If you set
OFFearlier, execute a
SET sql_log_bin = ONstatement. If you restarted the master to disable the binary log, restart it with
--log-bin, and without enabling the
skip_networkingsystem variable so that clients and slaves can connect.
Restart the slaves, this time without the
If you are upgrading an existing replication setup from a version
of MySQL that does not support global transaction identifiers to a
version that does, you should not enable GTIDs on either the
master or the slave before making sure that the setup meets all
the requirements for GTID-based replication. For example
server_uuid, which was added in
MySQL 5.6, must exist for GTIDs to function correctly. See
Section 184.108.40.206, “Setting Up Replication Using GTIDs”, which contains
information about converting existing replication setups to use
It is not recommended to load a dump file when GTIDs are enabled
on the server (
your dump file includes system tables.
mysqldump issues DML instructions for the
system tables which use the non-transactional MyISAM storage
engine, and this combination is not permitted when GTIDs are
enabled. Also be aware that loading a dump file from a server with
GTIDs enabled, into another server with GTIDs enabled, causes
different transaction identifiers to be generated.