pt-table-checksum can't complete

Polyglot Projects Percona Toolkit
1

Hi

I am running pt-table-checksum, I am getting some errors which I can’t make sense of. What is it waiting for ?

Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain

Many thanks

Best Regards

Kubilay

2

I am running into the same problem…

Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain

I keep seeing this in the output of pt-table-checksum. The table it is stuck on has 10 rows. The process list on the master says the checksum query has been sleeping for over an hour. There is no replication lag between master and slave. So what is it waiting on? Here is my example command:

pt-table-checksum -u user -p pass -h masterip --set-vars innodb_lock_wait_timeout=50 --nocheck-plan --no-check-binlog-format --chunk-size-limit 100.0 --chunk-time 10.0 --nocheck-replication-filters > checksum_output.log 2> checksum_errors.log

3

Hi,

Can you provide pt-table-checksum version + MySQL/Percona version + full checksum output log.

4

I have the same problem

pt-table-checksum 2.2.13

mysql --version

mysql Ver 14.14 Distrib 5.6.21-70.1, for debian-linux-gnu (x86_64) using EditLine wrapper
pt-table-checksum --no-check-binlog-format --databases my_xx --tables transfer --nocheck-replication-filters --recursion-method=processlist --no-check-slave-tables
Cannot connect to h=10.25.3.69
Cannot connect to h=10.25.7.58
Replica lag is 75 seconds on 53.xx.xx. Waiting.
Replica lag is 49 seconds on 53.xx.xx. Waiting.
Replica lag is 79 seconds on 53.xx.xx. Waiting.
Replica lag is 109 seconds on 53.xx.xx. Waiting.
Replica lag is 73 seconds on 53.xx.xx. Waiting.
Replica lag is 31 seconds on 53.xx.xx. Waiting.
Replica lag is 4 seconds on 53.xx.xx. Waiting.
Checksumming my_xx.transfer: 0% 14:05:58 remain
Checksumming my_xx.transfer: 13% 25:06 remain
Checksumming my_xx.transfer: 27% 12:12 remain
Checksumming my_xx.transfer: 42% 06:58 remain
Checksumming my_xx.transfer: 56% 04:17 remain
Checksumming my_xx.transfer: 72% 02:21 remain
Checksumming my_xx.transfer: 94% 00:22 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain
Waiting to check replicas for differences: 0% 00:00 remain

5

@PavelVD, make sure to check if you have database my_xx and table transfer on the slaves. Schema and table differences

The tool presumes that schemas and tables are identical on the master and all replicas. Replication will break if, for example, a replica does not have a schema that exists on the master (and that schema is checksummed), or if the structure of a table on a replica is different than on the master.

6

I ran into the same problem testing if after modifying a row on the slave (for testing purposes of course!)… it was simply waiting for me to commit the transaction!!!