Raise an error when transaction log wraps around before being processed by xtrabackup

Bug #805593 reported by Alexey Kopytov on 2011-07-04
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov

Bug Description

Currently when xtrabackup discovers that the transaction log has wrapped around before all log records have been copied (that is, the log copying thread is too late due to either load or the log files being too small) , xtrabackup prints the following message and the continues without failures (just printing the same message over and over until the log copying thread is terminated):

>> ###Warning###: The copying transaction log migh be overtaken already by the target.
>> : Waiting log block no 16732, but the bumber is already 20820.
>> : If the number equals 16732 + n * 4088, it should be overtaken already.

What it should do instead is to make the entire backup process fail, because hitting that condition can never result in a valid backup.

Related branches

affects: percona-server → percona-xtrabackup
tags: added: cr i17015
bcx (casper) wrote :

I'd like to add that a more verbose error message how to increase the innodb_log_file_size would be nice.

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers