innobackupex unable to capture slave info on incremental backups
Bug #857788 reported by
Lachlan Mulcahy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Undecided
|
Lachlan Mulcahy | ||
| 1.6 |
Fix Released
|
Undecided
|
Lachlan Mulcahy | ||
| 2.0 |
Fix Released
|
Undecided
|
Lachlan Mulcahy | ||
Bug Description
Trying to use the fix for this bug, which should enable capturing slave info with incremental backups...
https:/
Makes innobackupex fail when attempting to write slave info seemingly with a mysql response timeout. The real reason for this is that there is no actively open MySQL connection when using --slave-slave-info and --incremental with innobackupex.
Attached is a patch for use against innobackupex as per xtrabackup-1.6 rev 281.
It simplifies the connection open and closing so that it's less confusing to know, depending on which options you are using, whether you need to open a fresh connection or not, just always try to reuse the same one.
Related branches
lp:~lachlan-mulcahy/percona-xtrabackup/1.6-bug857788
- Alexey Kopytov (community): Approve
-
Diff: 63 lines (+13/-10)1 file modifiedinnobackupex (+13/-10)
Revision history for this message
| Lachlan Mulcahy (lachlan-mulcahy) wrote | #1 |
Revision history for this message
| Lachlan Mulcahy (lachlan-mulcahy) wrote | #2 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
Going to just make a branch for this and propose a merge..