… reasons and indeed because there is little validation (ie no checksums) in the replication there are multiple reasons for bad event… as described and when use Maatkit mk-table-checksum to check what tables are out of sync and when use mk-table-sync to resync them. Last…
Post: Why audit logging with triggers in MySQL is bad for replication
September 29, 2008 By 10 Comments
… was using Maatkit‘s mk-table-checksum to check his slave data was indeed a fair copy of that of the master. mk-table-checksum –algorithm=BIT_XOR h=hostname.local,u=root,p=xxx –replicate=checksum.checksum –emptyrepltbl –chunksize=500000 –databases…
Post: The story of one MySQL Upgrade
October 8, 2010 By 8 Comments
… is in sync to begin with to avoid false positives. mk-table-checksum is a tool to do it. It turned out replication… slave at the same position and used mk-table-checksum to ensure the data is in sync. mk-table-checksum can use replication to check consistency… than upgrade from MySQL 5.0 to 5.1 Also, Maatkit is Awesome, though I believe you know already.
Comment: Getting History of Table Sizes in MySQL
December 9, 2010 By 13 Comments
Maatkit‘s mk-find has features to iterate the tables and insert various information from them, just as you’ve described. Another advantage of this is that you won’t get false-positive checksum differences, which you’ll get if you let INSERT..SELECT replicate.
