Replication can get out of sync without warning. If you are using a slave for backup, disaster recovery, or even read-scaling, you want to make sure the slave has the same data as the master.
We will show the procedure we developed to use mk-table-checksum to minimize locking and slave lag that would be caused by locking large tables. We will discuss the problems we have run into with mk-table-checksum and how we have gotten around or fixed the issues—including when a table cannot be split into pieces and false positives generated in the MySQL error log.
Whether you use statement-based replication (the default), row-based replication or the mixed method, you can use mk-table-checksum to ensure your slave is in sync with your master. You can also use it even if your slave is lagging behind your master.
We will also show you how to fix the problems you encounter.
Been working with different RDBMS since early years in the university. Acted as a database developer for an accounting system for Donetsk National University in Ukraine.
Got the taste for MySQL while working as a DBA for Sonopia Corp.
Currently helping people all over the world to solve problems with their MySQL systems at The Pythian Group. And helping people, is what I like to do the most :)
Comments on this page are now closed.
For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at firstname.lastname@example.org
For media-related inquiries, contact Maureen Jennings at email@example.com
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the O'Reilly MySQL Conference newsletter (login required).
View a complete list of O'Reilly MySQL Conference contacts.