Reduce Replication Delay when Taking Backup from Slave
Bug #1182726 reported by
Jervin R
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Vlad Lesin | ||
| 2.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
| 2.1 |
Fix Released
|
High
|
Vlad Lesin | ||
Bug Description
This is the case for development request for xtrabackup to be able to combine the capabilities of --no-lock, --slave-info and --safe-slave-backup where the latter will be shorter as it will only take place during the last part of the log copying thread phase. However this is still subject to the limitations of --no-lock as such the user should be aware there should be no DDLs or MyISAM changes to take a consistent backup.
Related branches
lp:~vlad-lesin/percona-xtrabackup/bug1182726-2.1
- Alexey Kopytov (community): Needs Fixing
-
Diff: 100 lines (+63/-14)2 files modifiedinnobackupex (+26/-14)
test/t/bug1182726.sh (+37/-0)
| tags: | added: 32003 |
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:/