Master/slave Replication Slave Fails To Connect To Master

(Doc ID 2222854.1)

Last updated on AUGUST 24, 2017

Applies to:

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

Symptoms

On : 5.7 version, Replication (General and Statement)

ACTUAL BEHAVIOR
---------------
Customer was setting up Master - Slave replication from a backup of the Master server. The customer started from a binlog position which didn't exit on the specified log.

Recommended to start rebuilding replication from a fresh copy of the Master

EXPECTED BEHAVIOR
-----------------------
Replication couldn't find the starting position on the binlog, it error out with non-relevant message.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. stop slave
2. change master to master_log_file='', master_log_position=


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot fail over to the slave, slave remained out of sync.





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