xtrabackup issues a "FLUSH TABLES WITH READ LOCK" during a backup

[Nikhil Manchanda]

By default, xtrabackup starts with the --suspend-at-end option, and lets it copy the InnoDB data files.

When xtrabackup finishes that, it executes FLUSH TABLES WITH READ LOCK. Then it begins copying the rest of the files.

The FLUSH TABLES WITH READ LOCK option is needed only for MyISAM tables, and if you are using only innodb tables, you're better off not making this call, and locking your tables unnecessarily.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/58062

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/58062
Committed: http://github.com/openstack/trove/commit/f15038ec83c80d3eec154bd8ad1aafeab60d5634
Submitter: Jenkins
Branch: master

commit f15038ec83c80d3eec154bd8ad1aafeab60d5634
Author: Nikhil Manchanda <email address hidden>
Date: Fri Nov 22 14:34:58 2013 -0800

    Added ability to pass custom command-line options to backup runner

    Added a new DictOpt field "backup_runner_options" to the trove config
    Custom command-line options for the backup runner can be passed in
    through this

    Closes-Bug: 1253849

    Change-Id: I2ea45aa4899da4126776ef14a9cb2f0328a9e544