Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 39.1Mb
PDF (A4) - 39.1Mb
PDF (RPM) - 38.3Mb
HTML Download (TGZ) - 10.7Mb
HTML Download (Zip) - 10.8Mb
HTML Download (RPM) - 9.4Mb
Man Pages (TGZ) - 223.5Kb
Man Pages (Zip) - 331.4Kb
Info (Gzip) - 3.6Mb
Info (Zip) - 3.6Mb
Excerpts from this Manual

MySQL 5.7 Reference Manual  /  ...  /  Replication Relay and Status Logs

16.2.4 Replication Relay and Status Logs

During replication, a slave server creates several logs that hold the binary log events relayed from the master to the slave, and to record information about the current status and location within the relay log. There are three types of logs used in the process, listed here:

  • The master info log contains status and current configuration information for the slave's connection to the master. This log holds information on the master host name, login credentials, and coordinates indicating how far the slave has read from the master's binary log.

    This log can be written to the mysql.slave_master_info table instead of a file, by starting the slave with master_info_repository=TABLE.

  • The relay log consists of the events read from the binary log of the master and written by the slave I/O thread. Events in the relay log are executed on the slave as part of the SQL thread.

  • The relay log info log holds status information about the execution point within the slave's relay log.

    This log can be written to the mysql.slave_relay_log_info table instead of a file by starting the slave with relay_log_info_repository=TABLE.

When tables are used for the slave status logs, a warning is given if mysqld is unable to initialize the replication logging tables, but the slave is allowed to continue starting. This situation is most likely to occur when upgrading from a version of MySQL that does not support slave logging tables to one in which they are supported.


Do not attempt to update or insert rows in the slave_master_info or slave_relay_log_info table manually. Doing so can cause undefined behavior, and is not supported.

Execution of any statement requiring a write lock on either or both of the slave_master_info and slave_relay_log_info tables is disallowed while replication is ongoing, while statements that perform only reads are permitted at any time.

If you set master_info_repository and relay_log_info_repository to TABLE, the mysql.slave_master_info and mysql.slave_relay_log_info tables are created using the transactional storage engine InnoDB. As a table, updates to the relay log info log are committed together with the transactions, meaning that the slave's progress information recorded in that log is always consistent with what has been applied to the database, even in the event of an unexpected server halt. The --relay-log-recovery option must be enabled on the slave to guarantee resilience. For more details, see Section 16.3.2, “Handling an Unexpected Halt of a Replication Slave”.