pt-table-checksum: First TIME includes time waited for slave to catch up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Triaged
|
Undecided
|
Unassigned |
Bug Description
2.1.5. This is cosmetic.
I had a broken slave when I fired up pt-table-checksum:
Replica lag is 20401 seconds on piro.ii.nl. Waiting.
Replica lag is 19223 seconds on piro.ii.nl. Waiting.
Replica lag is 17271 seconds on piro.ii.nl. Waiting.
Replica lag is 16169 seconds on piro.ii.nl. Waiting.
Replica lag is 10468 seconds on piro.ii.nl. Waiting.
Replica lag is 6983 seconds on piro.ii.nl. Waiting.
TS ERRORS DIFFS ROWS CHUNKS SKIPPED TIME TABLE
10-31T23:35:34 0 0 0 1 0 6583.534 aal.a_files
It seems that the first value in the TIME column includes the time waiting for the slave to start up, the next run didn't have it.
TS ERRORS DIFFS ROWS CHUNKS SKIPPED TIME TABLE
10-31T23:43:52 0 0 0 1 0 0.069 aal.a_files
Ahyup, stopping/starting the slave triggered it again:
Replica piro.ii.nl is stopped. Waiting.
TS ERRORS DIFFS ROWS CHUNKS SKIPPED TIME TABLE
10-31T23:55:56 0 0 0 1 0 13.137 aalborg.a_files
tags: | added: pt-table-checksum replication-lag wrong-output |
Changed in percona-toolkit: | |
status: | New → Triaged |
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PT-1041