"The log was not applied to the intended LSN", lsn for incremental is ahead of scanned LSN

[Nickolay Ihalainen]

The problem is related to https://bugs.launchpad.net/percona-xtrabackup/+bug/1414221

During backup:
xtrabackup: The latest check point (for incremental): '32612243417684'
xtrabackup: Stopping log copying thread.
.>> log scanned up to (32612243417600)

At apply log stage:
xtrabackup: Log applied to lsn 32612243417578
xtrabackup: The intended lsn is 32612243417600

As you can see log scanning stopped before latest checkpoint and this could break incremental backups and probably it's a symptom for the original issue with non-applied last 106 bytes of xtrabackup transaction log.

I'm not able to reproduce this issue on a staging server, but it's not something related to high load (just 350 commits per second, 250 insert per second)

[Nickolay Ihalainen (ihanick)]

The problem frequently happens with Xtrabackup 2.2.6 and 2.2.10 with and without LOCK TABLES FOR BACKUP.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1320