Feature request: Put a limit on the amount of time XtraBackup will lock tables

[Fran Garcia]

Hi,

The new improvements to XtraBackup (http://www.percona.com/doc/percona-xtrabackup/2.1/innobackupex/improved_ftwrl.html#improved-ftwrl) are a great help for limiting the impact of FTWRL on a live DB, but once the lock has been acquired it won't be released until the backup process has completed.

This process might be slowed down by any of the following issues:
- Someone create a non-InnoDB table that needs to be backed up while the lock is held.
- Network issues between the db host and the backup destination, making the transfer slower than it should.
- High IO on the server slowing down the process
- Having a ridiculous amount of tables and/or a combination of all of the above.

Having an option to limit the amount of time XtraBackup will hold the lock before aborting the backup process would be a really useful thing to do, so I can be sure that the backups won't lock my live db for more than a minute.

[Alexey Kopytov (akopytov)]

Looks like a reasonable feature request to me. Thanks.

[Alexey Kopytov (akopytov)]

See also https://blueprints.launchpad.net/percona-xtradb-cluster/+spec/trigger-timeout-of-ftwrl-on-sst

[Shahriyar Rzayev (rzayev-sehriyar)]

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