Comment 1 for bug 1711565

I am able to reproduce this on one of our slaves (not on the others), MySQL version and Xtrabackup version being the same.

Apparently it is due, at least in this case, to a mix of insert and truncate table instructions.
I believe the truncate table is the key to the bug here....

Just create the schema, run the attached script on the master, and run an xtrabackup incremental on the slave; hopefully it will break on that table with error posted above.

We run the incremental as follows:

/usr/bin/innobackupex --defaults-file=/etc/my.cnf --no-version-check --incremental --no-backup-locks --slave-info --no-timestamp --parallel=1 --socket=/db/data/mysql.sock --user=backup --password=amended --tmpdir=/storage/backup/tmp --extra-lsndir=/storage/backup/lsn_incr --incremental-basedir=/storage/backup/lsn_incr /storage/backup/incr

Versions:

mysqld Ver 5.7.19-17 for Linux on x86_64 (Percona Server (GPL), Release 17, Revision e19a6b7b73f)
xtrabackup version 2.4.8 based on MySQL server 5.7.13 Linux (x86_64) (revision id: 97330f7)