Execute FLUSH ENGINE LOGS before finalizing the REDO log copy
Bug #1320685 reported by
Alexey Kopytov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Alexey Kopytov | ||
| 2.1 |
Fix Released
|
High
|
Alexey Kopytov | ||
| 2.2 |
Fix Released
|
High
|
Alexey Kopytov | ||
Bug Description
Currently XtraBackup does not flush InnoDB REDO log buffer before finalizing the log copy. It only becomes a problem when the binary log coordinates are used after restoring from a backup: the actual data files state after recovery may be inconsistent with the binary log coordinates.
Related branches
lp:~akopytov/percona-xtrabackup/bug1320685-2.1
- Alexey Kopytov (community): Approve
-
Diff: 54 lines (+23/-1)1 file modifiedinnobackupex.pl (+23/-1)
lp:~akopytov/percona-xtrabackup/bug1320685-2.2
- Alexey Kopytov (community): Approve
-
Diff: 66 lines (+23/-3)2 files modifiedstorage/innobase/xtrabackup/innobackupex.pl (+21/-1)
storage/innobase/xtrabackup/test/t/backup_locks.sh (+2/-2)
| tags: | added: low-hanging-fruit |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/