On Wed, Dec 24, 2008 at 2:31 AM, Jake Maul <jakem...@gmail.com> wrote: > Slightly more complicated (and also probably more accurate- the time > reported by show slave status is known to be unreliable in some cases) > would be a script that inserts a row into a table, then check the > slave over and over till it arrives. Or even better, insert 2 > values... a timestamp that *you* provide (in a shell script, something > like $(date) would work) and a timestamp generated by MySQL.... > assuming the times are syncronized on the master, slave, and the box > you're inserting from, when the insert hits the slave it'll generate > it's own timestamp, which you can then subtract *your* timestamp from. > > There's also a tool in maatkit which does replication tracking, > although I've not yet used it. Judging by the other tools in that > package though, it's probably pretty decent :).
It is mk-heartbeat, and it does pretty much what you described, although it's been tweaked to be slightly more complex to suit various real-world scenarios. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
