MySQL 5.6 has an impressive list of improvements. Among them,
replication checksums caught my attention as it seems that many
people misunderstand the real added value of this new feature. I
heard people think that with replication checksums, data
integrity between the master and its replicas is now enforced. As
we’ll see, it’s not that easy.
First, here are a few common reasons why data integrity may be
broken (the list is not exhaustive):
- writes executed on a replica instead of the master
- non deterministic queries
- bad use of replication filters
- rollback of transactions mixing transactional and
non-transactional tables
The real problem is that replication may keep on running without
error, not letting you know that all servers no longer have the
same data.
Will replication checksums detect such problems? Unfortunately,
no, they won’t.
That …
[Read more]