# Skipping table - it would be checksummed in 1 chunk but replicas have too many rows

**URL:** <https://forums.percona.com/t/skipping-table-it-would-be-checksummed-in-1-chunk-but-replicas-have-too-many-rows/3807>\
**Category:** Percona Toolkit\
**Created:** [October 8, 2014, 3:37pm UTC](https://forums.percona.com/t/skipping-table-it-would-be-checksummed-in-1-chunk-but-replicas-have-too-many-rows/3807 "2014-10-08T15:37:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![epinc](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@epinc](https://forums.percona.com/u/epinc)\
**Post date:** [October 8, 2014, 3:37pm UTC](https://forums.percona.com/t/skipping-table-it-would-be-checksummed-in-1-chunk-but-replicas-have-too-many-rows/3807/1 "2014-10-08T15:37:28Z")

</div>

I am getting this error on a series of random tables every night I try to run the pt-table-checksum script

Every night the tables affected are different, and these tables are not in use by anyone else when the script is run

I manually count the records on each replica and they match the server

What could be the issue here?

Skipping table XXXX because on the master it would be checksummed in one chunk but on these replicas it has too many rows:  
88687 rows on Replica1  
86422 rows on Replica2

---

<div class="post-metadata">

**Author:** ![mirfan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mirfan/32/16890_2.png) [@mirfan](https://forums.percona.com/u/mirfan)\
**Post date:** [October 14, 2014, 1:23am UTC](https://forums.percona.com/t/skipping-table-it-would-be-checksummed-in-1-chunk-but-replicas-have-too-many-rows/3807/2 "2014-10-14T01:23:12Z")

</div>

Make sure all your tables should contains primary or unique key as [pt-table-checksum](http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html) requires primary key or unique key to divide a table into chunks. Ever changing table statistics can be problem. Try with trun off innodb\_stats\_on\_metadata before checksum. Try setting up different value for [–chunk-size-limit](http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html#cmdoption-pt-table-checksum--chunk-size-limit) and [–chunk-time](http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html#cmdoption-pt-table-checksum--chunk-time) although this can increase server load because of bigger chunks. Running ANALYZE TABLE before checksum may help too. And it’s good idea to run with PTDEBUG option to enable debugging output for pt-table-checksum.

---

<div class="post-metadata">

**Author:** ![epinc](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@epinc](https://forums.percona.com/u/epinc)\
**Post date:** [October 17, 2014, 8:56pm UTC](https://forums.percona.com/t/skipping-table-it-would-be-checksummed-in-1-chunk-but-replicas-have-too-many-rows/3807/3 "2014-10-17T20:56:10Z")

</div>

Hi! Thank you very much for your reply. I will try those suggestions
