Issues
- pt-table-sync doesn't work on JSON columnsPT-2325
- pt-table-sync generates empty replace commandsPT-1727
- Authentication plugin 'caching_sha2_password' cannot be loadedPT-1724Resolved issue: PT-1724
- pt-table-sync is not attempting to sync data between two tables even though there are row differences.PT-1703
- Inconsistent creation of toolkit tables - pt-table-syncPT-1659Resolved issue: PT-1659Carlos Salguero
- LP #1666531: Failed to debug with utf8 charsPT-1413Resolved issue: PT-1413
- LP #1647909: pt-table-sync - incorrect return code on errorPT-1402
- LP #1622663: pt-table-sync: Please add to documentation, that "REPLACE INTO" will fire "insert trigger" in mysql variantsPT-1384
- LP #1620509: The table '__maatkit_char_chunking_map' is fullPT-1383
- LP #1595912: pt-table-sync and pt-table-checksum do not allow to specify user to check slave if --recursion-method processlist or host is usedPT-1367Resolved issue: PT-1367
- LP #1592903: pt-table-sync accept user variablesPT-1357Resolved issue: PT-1357
- LP #1592608: Large BLOB/TEXT/BINARY Produces NULL ChecksumPT-1356Resolved issue: PT-1356
- LP #1570710: pt-table-checksum got error with gtidPT-1341Resolved issue: PT-1341
- LP #1553456: pt-table-sync does take into account timezone dependent columnsPT-1333
- LP #1550114: pt-table-sync print update sql for one row of table but they are totally same between master and slavePT-1331Resolved issue: PT-1331
- LP #1488735: Setting "--chunk-size=1000k" causes exception when empty table syncedPT-1300Resolved issue: PT-1300
- LP #1437775: pt-table-sync doesn't escape replicate tablePT-1275
- LP #1428549: pt-table-sync: unneeded replication of temporary tablesPT-1270Resolved issue: PT-1270
- LP #1426629: pt-table-sync quotes float values, can't syncPT-1268
- LP #1340649: pt-table-sync checks changing binlog_format on slaves and exists if that does not work. (RDS)PT-1233
- LP #1331940: Pt-table-sync was not workingPT-1229Resolved issue: PT-1229
- LP #1311584: pt-table-sync --ignore-columns case sensitivityPT-1221
- LP #1275034: pt-table-sync reports 'wide character in print' and terminatesPT-1205Resolved issue: PT-1205Sveta Smirnova
- LP #1268632: pt-table-sync generates lots of errors in MariaDB logsPT-1197
- LP #1266896: pt-table-sync port problemPT-1194Resolved issue: PT-1194Sveta Smirnova
- LP #1263168: pt-table-sync can't sync rows due to deadlocksPT-1191Resolved issue: PT-1191
- LP #1247677: --recursion-method documentation or behaviour incorrectPT-1168
- LP #1239048: pt-table-sync doesn't respect bin-log formats of independent serversPT-1160
- LP #1234661: pt-table-sync cant get table structure from viewPT-1156Resolved issue: PT-1156
- LP #1229451: pt-table-sync does not dump bit values properly with --printPT-1155
- LP #1229086: pt-table-sync char-chunking works despite docsPT-1154
- LP #1204562: pt-table-sync does not sync bidirectional with primary key BINARY(16)PT-1135Resolved issue: PT-1135
- LP #1185124: pt-table-sync --print option binary columns not readable in outputPT-1118
- LP #1150477: pt-table-sync --hex-blob option should also be used for geo and bitPT-1088
- LP #1150452: pt-table-sync fails for point primary keysPT-1087
- LP #1083621: Sync tables from one database with tables from another database on the same or different serverPT-1053
- LP #1060590: Default value for sleep is a hash, not a real valuePT-1030Resolved issue: PT-1030
- LP #1042036: pt-table-sync + stock mysql 5.5.25a errorPT-1016Resolved issue: PT-1016
- LP #1030053: pt-table-sync does not detect data difference using CRC32 hashPT-1007
- LP #1026664: pt-table-sync prepare_sync_cylce failsPT-1004Resolved issue: PT-1004
- LP #1026662: pt-table-sync fails setting NO_AUTO_VALUE_ON_ZEROPT-1003Resolved issue: PT-1003
- LP #1003323: pt-table-sync: Deep recursion on subroutine "SchemaIterator::_iterate_dbh"PT-979Resolved issue: PT-979
- LP #1002364: pt-table-sync doesn't work with uppercase index namesPT-977Resolved issue: PT-977
- LP #982381: errors running pt-table-sync as non-rootPT-958Resolved issue: PT-958Carlos Salguero
- LP #953101: TableSyncNibble fails to quote varchar columns in primary keyPT-947Resolved issue: PT-947
- LP #947987: Some tools still use removed package (MySQLDump)PT-945Resolved issue: PT-945
- LP #890650: pt-table-sync doesn't recursively find slaves as opposed to pt-table-checksumPT-896
- LP #870510: pt-table-sync cannot connected slavePT-880Resolved issue: PT-880
- LP #869032: pt-table-sync ambiguous error message on permission checkPT-879Resolved issue: PT-879
- LP #1439842: [feature] pt-table-sync lacks --ignore-tables-regex optionPT-862Resolved issue: PT-862
50 of 80
Downgrade on same major version fails - 5.7.24 Donor and 5.7.20 Joiner
Won't Do
General
Escalation
General
Escalation
Description
Environment
PXC1 - version 5.7.24
PXC2 - version 5.7.20 (downgraded from v5.7.24)
AFFECTED CS IDs
245560
Attachments
2
Smart Checklist
Details
Assignee
UnassignedUnassignedReporter
Jericho RiveraJericho RiveraAffects versions
Priority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
Jericho Rivera
Jericho RiveraAffects versions
Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created February 6, 2019 at 7:25 AM
Updated March 6, 2024 at 10:18 PM
Resolved February 28, 2023 at 11:24 AM
Activity
Show:
Kamil HolubickiFebruary 28, 2023 at 11:24 AM
Downgrade is not supported.
Downgraded PXC 5.7.24 to PXC 5.7.20 will result to failed SST from 5.7.24 donor to 5.7.20 joiner. See attached logs from pxc1 and pxc2. Upgraded pxc2 back to 5.7.24 and it works.
How to repeat:
setup PXC 5.7.24 cluster
create table t1 (id int primary key auto_increment, s varchar(100)) engine=innodb;
insert data
downgrade on node to PXC 5.7.20
insert data on one of PXC 5.7.24 nodes to trigger the IST when 5.7.20 rejoins
start PXC 5.7.20 node