We do a lot of stuff that MySQL replication does not really like. We should probably not do that stuff, or at least have a consistent story about why we're doing that stuff.
Stuff it's complaining about:
- INSERT ... ON DUPLICATE KEY UPDATE on tables with multiple unique keys.
- DELETE statements with LIMITs (?)
160414 20:50:06 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO `repository_statusmessage` (repositoryID, statusType, statusCode, parameters, epoch) VALUES ...
INSERT INTO `cache_general` (cacheKeyHash, cacheKey, cacheFormat, cacheData, cacheCreated, cacheExpires) VALUES ...
Most Garbage Collection
[Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: DELETE FROM `metamta_receivedmail` WHERE dateCreated < 1452890862 LIMIT 100