innobackupex unable to capture slave info on incremental backups

Reported by Lachlan Mulcahy on 2011-09-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Undecided
Lachlan Mulcahy
1.6
Undecided
Lachlan Mulcahy
2.0
Undecided
Lachlan Mulcahy

Bug Description

Trying to use the fix for this bug, which should enable capturing slave info with incremental backups...

https://bugs.launchpad.net/percona-xtrabackup/+bug/834657

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.

Going to just make a branch for this and propose a merge..

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers