Re: measuring slave lag without sysdate() - 4.1.13
Hi Rick,
That's exactly what I have been using. Unfortunately it appears that before MySQL 5, both NOW() and SYSDATE() are affected by the SET TIMESTAMP that is added to the binlog for replication.
Consequently, the slave insert shows exactly the same time as the master insert, no matter when the slave insert actually takes place.
This is changed in MySQL 5 - SYSDATE() is no longer affected by SET TIMESTAMP, and does reflect exactly when the insert actually took place.
So, my question is, is there another trick I can use to monitor the slave lag until I can get those involved to upgrade to 5+?
thanks.
Subject
Views
Written By
Posted
3077
February 07, 2012 05:54AM
1005
February 08, 2012 02:09AM
Re: measuring slave lag without sysdate() - 4.1.13
1174
February 08, 2012 04:26AM
1120
February 09, 2012 11:05AM
1460
February 09, 2012 02:08PM
905
February 11, 2012 12:00AM
923
February 20, 2012 06:25AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.