MySQL Bugs: #39531: Seconds behind master is continiously increasing

Bug #39531	Seconds behind master is continiously increasing
Submitted:	19 Sep 2008 7:47	Modified:	29 Dec 2011 16:21
Reporter:	Martin Boer	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	5.0.51a-12-log	OS:	Linux (default 'lenny' version)
Assigned to:		CPU Architecture:	Any

Description:
Hi there,
I couldn't find this bug in the reported bugs, nor information on the internet how to solve it so I figured this bug needs to reported.  

We have one master and 3 slaves.
The slaves are identical Debian Lenny chroots with the default MySQL in it.
On 2 of the slaves we notice since a couple of days that when using 'show slave status \G;' the number is increasing. The number keeps increasing until the master rotates its Master Log file. After that, the counter resets and the game repeats itself.
The reason why I report this bug as S3 is because the slaves themselves do a fine job: The Relay Log Position keeps up with the master and when we created and dropped a table on the master it showed up and disappearred on all 3 the slaves almost directly.

So, we have one master, 3 slaves and everything works like a charm, except that on 2 of the slaves the counter 'seconds behind master' keeps increasing.

How to repeat:
Don't know

Suggested fix:
Don't know

Thank you for the report.

But version 5.0.51 is a bit old. Please try with current version 5.0.67 and if problem still exists send configuration and error log files from all slaves and master.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

I have the same issue. 1 master, 2 slaves, 1 slave has an increasing value for this.

Server version: 5.1.49-3 (Debian)

David,

thank you for the feedback.

There can be thousands of reason why this time is increasing. Most common are slow network between master and slave and cases when slave performs much slower than master. These 2 are not MySQL bugs.

To prove this is MySQL bug, so fix it, we need repeatable test case or, at least, detailed explanation of the problem and all configuration and error log files from both master and slave.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".