Replication slave does not reconnect to master for a long time (30-60 minutes) (Doc ID 1950090.1)

Last updated on AUGUST 12, 2015

Applies to:

MySQL Server - Version 4.0 to 5.6 [Release 4.0 to 5.6]
Information in this document applies to any platform.


A replication slave server that was previously working does not receive or process any updates from it's master, however no issues are apparent from the SHOW SLAVE STATUS output except that the current position (Master_Log_file, Read_Master_Log_Pos) is not advancing and does not match the master's position.  This may occur intermittently or occasionally, for up to 1 hour (or the value of slave_net_timeout, if different from the default 3600 seconds).

If this issue has occurred in the past, you may note that the slave reconnected to the master without showing any signs of a disconnection.  You'll simply see a new note about reconnection only:


This event typically occurs when the connection to the master server was interrupted by either complete server crash, hard restart or a network outage.  In these cases the TCP session is often not actively reset as it would be in a graceful shutdown.


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