xtrabackup issues a "FLUSH TABLES WITH READ LOCK" during a backup
Bug #1253849 reported by
Nikhil Manchanda
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
Nikhil Manchanda |
Bug Description
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.
summary: |
- xtrabackup locks innodb tables with "FLUSH TABLES WITH READ LOCK" at the - end of a backup + xtrabackup issues a "FLUSH TABLES WITH READ LOCK" at the end of a backup |
summary: |
- xtrabackup issues a "FLUSH TABLES WITH READ LOCK" at the end of a backup + xtrabackup issues a "FLUSH TABLES WITH READ LOCK" during a backup |
Changed in trove: | |
assignee: | nobody → Nikhil Manchanda (slicknik) |
Changed in trove: | |
milestone: | none → icehouse-1 |
Changed in trove: | |
importance: | Undecided → Medium |
Changed in trove: | |
milestone: | icehouse-1 → icehouse-2 |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | icehouse-2 → 2014.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/58062
Review: https:/