My Oracle Support Banner

MySQL Group Replication Error Could not find target log file mentioned in relay log info in the index file (Doc ID 2443305.1)

Last updated on NOVEMBER 12, 2021

Applies to:

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

Symptoms

We are unable to re-add instance into an innodb cluster after changing the nic/hostname of the server.

The following error is given:

2018-01-19T01:45:31.066251Z 0 [ERROR] Failed to open the relay log'./foo-relay-bin-group_replication_applier.000002' (relay_log_pos 3541).
2018-01-19T01:45:31.066272Z 0 [ERROR] Could not find target log file mentioned in relay log info in the index file './FOO-group_replication_applier.index' during relay log initialization.
2018-01-19T01:45:31.099316Z 0 [ERROR] Slave: Failed to initialize the master info structure for channel 'group_replication_applier'; its record may still be present in 'mysql.slave_master_info' table, consider deleting it.
2018-01-19T01:45:31.249836Z 0 [ERROR] Failed to open the relay log './foo-relay-bin-group_replication_recovery.000001' (relay_log_pos 4).
2018-01-19T01:45:31.249856Z 0 [ERROR] Could not find target log file mentioned in relay log info in the index file'./FOO-group_replication_recovery.index' during relay log initialization.

Changes

 The error occurs after changing the hostname from foo-db02 to FOO-DB02 when DNS was updated.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.