Avoid Problems with Replication Lag Reporting by Syncing System Clocks
Last updated on JULY 10, 2016
Applies to:MySQL Server - Version 4.0 and later
Information in this document applies to any platform.
System clocks on slave and master being out of sync can result in erroneous reporting of "seconds behind master" on slave servers, with the lag increasing further as the clocks drift further apart.
This problem can be avoided by keeping server clocks synced with a network time source. On Linux systems, this could be accomplished by properly configuring and running the NTP service.
Eliminate erroneous reporting of replication lag on the slave due to unsynced system clocks.
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