Issues
- LP #1214337: pt-table-checksum doesn't respect --chunk-size-limitPT-1143
- LP #1212364: pt-archiver --bulk-delete doc issuePT-1140Resolved issue: PT-1140
- LP #1089173: pt-online-schema-change prints scary/misleading message while pausing for slave lagPT-1056
- LP #869032: pt-table-sync ambiguous error message on permission checkPT-879Resolved issue: PT-879
- LP #1045317: pt-online-schema-change doesn't report how many warnings it suppressedPT-576Resolved issue: PT-576
- LP #1105077: pt-table-checksum: Confusing error message with binlog_format ROW or MIXED on slavePT-351Resolved issue: PT-351
- LP #944051: pt-table-checksum has ambiguous exit statusPT-300Resolved issue: PT-300
7 of 7
LP #1214337: pt-table-checksum doesn't respect --chunk-size-limit
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Details
Assignee
UnassignedUnassignedReporter
lpjirasynclpjirasync(Deactivated)Priority
LowComponents
Details
Details
Assignee
Unassigned
UnassignedReporter
lpjirasync
lpjirasync(Deactivated)
Priority
LowComponents
Smart Checklist
Smart Checklist
Smart Checklist
Created January 24, 2018 at 7:43 PM
Updated December 21, 2022 at 4:55 PM
Activity
lpjirasyncJanuary 24, 2018 at 7:43 PM
**Comment from Launchpad by: Daniel Nichter on: 30-10-2013 17:25:34
Yes, the docs are a little odd because they say 1 is the minimum value, but the next paragraph says "use zero to disable". I'll re-review.
lpjirasyncJanuary 24, 2018 at 7:43 PM
**Comment from Launchpad by: Kenny Gryp on: 25-10-2013 15:18:52
This was already reported in bug 938660. This at least is some documentation issue.
chunk-size-limit becomes 1 if you set it to 0.
lpjirasyncJanuary 24, 2018 at 7:43 PM
**Comment from Launchpad by: Rob Wagner on: 25-10-2013 12:48:36
I'm also seeing this issue on PT 2.1.5.
**Reported in Launchpad by Marcelo Altmann last update 30-10-2013 17:26:08
I'm invoking pt-table-checksum 2.2.4 as follow:
pt-table-checksum --recursion-method=hosts --set-vars innodb_lock_wait_timeout=50 --replicate dba_tools.rep_checksum --no-check-plan --chunk-size-limit=0
I'm getting an error in one single table:
08-20T06:09:14 Skipping table production.Products because on the master it would be checksummed in one chunk but on these replicas it has too many rows:
170573 rows on slave1
189670 rows on slave2
154844 rows on slave3
189998 rows on slave4
189380 rows on slave5
188190 rows on slave6
The current chunk size limit is 150403 rows (chunk size=150403 * chunk size limit=1).
If I run SELECT COUNT FROM production.Products it returns the same result for master and all replicas.
As I'm invoking pt-table-checksum with --chunk-size-limit=0, why it's using chunk size limit=1 ? I expect it to disable the chunk size check.
All servers are running 5.0.96-enterprise-log MySQL Enterprise Server (Commercial)