Slave is Stopped or Killed in MTS Mode; Failed to Initialize the Master Info Channel (Doc ID 2113131.1)

Last updated on MARCH 16, 2016

Applies to:

MySQL Server - Version 5.7 and later
Information in this document applies to any platform.

Symptoms

The follow errors appear in the error log and the slave is not running correctly:

2016-02-08T21:01:08.926165Z 0 [Note] Slave: MTS group recovery relay log info group_master_log_name mysql-bin.000069, event_master_log_pos 277425203.
2016-02-08T21:01:08.926181Z 0 [ERROR] --relay-log-recovery cannot be executed when the slave was stopped with an error or killed in MTS mode; consider using RESET SLAVE or restart the server with --relay-log-recovery = 0 followed by START SLAVE UNTIL SQL_AFTER_MTS_GAPS
2016-02-08T21:01:08.926355Z 0 [ERROR] Slave: Failed to initialize the master info structure for channel 'myhostrep'; its record may still be present in 'mysql.slave_master_info' table, consider deleting it. Aborting initialization of other channels.
2016-02-08T21:01:08.926453Z 0 [ERROR] Failed to create or recover replication info repositories.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms