Issues
- LP #1229086: pt-table-sync char-chunking works despite docsPT-1154
- LP #1214337: pt-table-checksum doesn't respect --chunk-size-limitPT-1143
- LP #1182180: pt-table-checksum fails when table is emptyPT-1114Resolved issue: PT-1114Carlos Salguero
- LP #1150452: pt-table-sync fails for point primary keysPT-1087
- LP #1061999: pt-online-schema-change errors out for large PKPT-1033Resolved issue: PT-1033
- LP #1030053: pt-table-sync does not detect data difference using CRC32 hashPT-1007
- LP #1002364: pt-table-sync doesn't work with uppercase index namesPT-977Resolved issue: PT-977
- LP #987495: pt-table-checksum: Switch to disable #-of-rows checks on slavesPT-963Resolved issue: PT-963
- LP #984753: pt-online-schema-change does not work well when there are gaps in the PK columnPT-961Resolved issue: PT-961
- LP #938660: pt-table-checksum chunk-size-limit of 0 does not disable chunk size limit checkingPT-938Resolved issue: PT-938
- LP #918051: chunk size error if you use --resume optionPT-919Resolved issue: PT-919
- LP #1130498: Chunking handles multi-column indexes poorlyPT-604Resolved issue: PT-604
- LP #1059732: pt-table-checksum doesn't test all hash functionsPT-586Resolved issue: PT-586
- LP #1003003: pt-online-schema-change uses different keys for chunking and triggersPT-534Resolved issue: PT-534
- LP #994002: pt-online-schema-change 2.1.1 doesn't choose the PRIMARY KEYPT-525Resolved issue: PT-525
- LP #987393: pt-table-checksum: Empy tables cause "undefined value as an ARRAY" errorsPT-522Resolved issue: PT-522
- LP #1199591: pt-table-checksum doesn't use non-unique index with highest cardinalityPT-362Resolved issue: PT-362
- LP #1034717: pt-table-sync division by zero error with varchar primary keyPT-324Resolved issue: PT-324
- LP #1010232: pt-table-checksum doesn't check the size of checksum chunksPT-318Resolved issue: PT-318
- LP #978432: pt-table-checksum ignoring primary keyPT-305Resolved issue: PT-305
- LP #918056: pt-table-sync false-positive error "Cannot nibble table because MySQL chose no index instead of the PRIMARY index"PT-289Resolved issue: PT-289
- LP #821673: pt-table-checksum doesn't include --where in min max queriesPT-252Resolved issue: PT-252
22 of 22
LP #1229086: pt-table-sync char-chunking works despite docs
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Details
Assignee
UnassignedUnassignedReporter
lpjirasynclpjirasync(Deactivated)Priority
LowFix versions
Details
Details
Assignee
Unassigned
UnassignedReporter
lpjirasync
lpjirasync(Deactivated)Priority
Fix versions
Smart Checklist
Smart Checklist
Smart Checklist
Created January 24, 2018 at 7:47 PM
Updated January 15, 2024 at 11:40 AM
Activity
lpjirasyncJanuary 24, 2018 at 7:47 PM
**Comment from Launchpad by: monty solomon on: 27-02-2015 18:36:33
pt-table-checksum does not complain about the table.
lpjirasyncJanuary 24, 2018 at 7:47 PM
**Comment from Launchpad by: monty solomon on: 27-02-2015 11:34:07
I am getting the following message from pt-table-sync 2.2.13
Failed to prepare TableSyncChunk plugin: Cannot chunk table using the character column channelguid, most likely because all values start with the same character. This table must be synced separately by specifying a list of --algorithms without the Chunk algorithm at pt-table-sync line 4049.
The channelguid column is the PK and is char(36) NOT NULL with table DEFAULT CHARSET=utf8
The values in the channelguid column start will hex 0-f inclusive.
**Reported in Launchpad by snowave last update 27-02-2015 18:36:34
the document says
Note that this algorithm will not work if chunking a char column where all the values start with the same character. In that case, the tool will exit and suggest picking a different algorithm.
i have a try
mysql> desc za;
---------------------------+---------------
Field
Type
Null
Key
Default
Extra
---------------------------+---------------
id
char(20)
YES
UNI
NULL
----------------+----+---+-------+------+
1 row in set (0.00 sec)
mysql> select * from za limit 5;
------------
id
------------
abc008LV
abc00tpYxz
abc00tQz
abc00uUaSp
abc01cFv
------------
5 rows in set (0.00 sec)
so can found the prefix of a row begins with abcoppose to the document says i think the tool will use nibble ALGORITHM,
TableSyncer:5807 8903 Getting best plugin
TableSyncer:5809 8903 Trying plugin Chunk
TableChunker:3703 8903 Possible chunk indexes in order: un_id
TableChunker:3723 8903 Exact chunkable: id on un_id
TableChunker:3727 8903 Ordering columns by order in tbl, PK first
TableChunker:3740 8903 Chunkable columns: id on un_id
TableChunker:3741 8903 Can chunk exactly: 1
TableSyncChunk:5028 8903 Can chunk on column id using index un_id
TableSyncer:5812 8903 Can sync with Chunk $VAR1 = {
chunk_col => 'id',
chunk_index => 'un_id'
};
you can see, it used chunk algorithm , could explain ?