My Oracle Support Banner

Mysql Replica Lag Increasing (Doc ID 2003083.1)

Last updated on MARCH 12, 2021

Applies to:

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

Symptoms

On : 5.1 version, Replication (General and Statement)

ACTUAL BEHAVIOR
---------------
mysql> show slave status\G
*************************** 1. row ***************************
....
  Master_Log_File: cryptop_popcorn_binlog.025683
  Read_Master_Log_Pos: 4
  Relay_Log_File: holbrook-relay-bin.112299
  Relay_Log_Pos: 162
  Relay_Master_Log_File: cryptop_popcorn_binlog.025683
  Slave_IO_Running: Yes
  Slave_SQL_Running: Yes
 ....
  Seconds_Behind_Master: 495317
Master_SSL_Verify_Server_Cert: No
.....

mysql> show slave status\G
*************************** 1. row ***************************
.....
  Master_Log_File: cryptop_popcorn_binlog.025682
  Read_Master_Log_Pos: 6832
  Relay_Log_File: holbrook-relay-bin.112310
  Relay_Log_Pos: 6909
  Relay_Master_Log_File: cryptop_popcorn_binlog.025682
  Slave_IO_Running: Yes
  Slave_SQL_Running: Yes
.....
  Seconds_Behind_Master: 0
.....



EXPECTED BEHAVIOR
-----------------------
Increasing sequential binary log numbers is what is required.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Get a range of binary logs.
2. Delete the last few binary logs.
3. Set the slave to start replicating from previous logs.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot replicate past the last valid binary log.

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
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.