Not a Bug
Details
Assignee
UnassignedUnassignedReporter
lpjirasynclpjirasync(Deactivated)Priority
Low
Details
Details
Assignee
Unassigned
UnassignedReporter
lpjirasync
lpjirasync(Deactivated)Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created January 24, 2018 at 6:58 PM
Updated February 4, 2018 at 2:05 AM
Resolved January 24, 2018 at 6:59 PM
**Reported in Launchpad by Mike Benshoof last update 25-03-2013 15:36:24
Running pt-table-checksum against the master repeatedly shows different chunks out of sync on the slave that are not found by pt-table-sync.
Details:
Table has timestamp column with ON UPDATE CURRENT_TIMESTAMP
Updates to table are done via an explicit transaction
Max timestamp from the ON UPDATE field generally matches the ts column from the checksum table (give or take a second) for the out of sync chunks
tx_isolation is REPEATABLE-READ on master/slave