Innobackupex with --safe-slave can start slave thread earlier
Bug #1284778 reported by
Sergei Glushchenko
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Sergei Glushchenko | ||
| 2.0 |
Fix Released
|
High
|
Sergei Glushchenko | ||
| 2.1 |
Fix Released
|
High
|
Sergei Glushchenko | ||
| 2.2 |
Fix Released
|
High
|
Sergei Glushchenko | ||
Bug Description
Currently slave thread started after xtrabackup finished log streaming which may take a lot of time. We should start slave thread right after log copying thread has stopped.
Related branches
lp:~sergei.glushchenko/percona-xtrabackup/2.0-BT39727-xb-bug1284778
- Alexey Kopytov (community): Approve
-
Diff: 18 lines (+2/-2)1 file modifiedinnobackupex (+2/-2)
lp:~sergei.glushchenko/percona-xtrabackup/2.1-BT39727-xb-bug1284778
- Alexey Kopytov (community): Approve
-
Diff: 19 lines (+2/-2)1 file modifiedinnobackupex.pl (+2/-2)
lp:~sergei.glushchenko/percona-xtrabackup/2.2-BT39727-xb-bug1284778
- Alexey Kopytov (community): Approve
| Changed in percona-xtrabackup: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| tags: | added: i39727 |
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:/