innobackupex does not handle non-slave mysql with safe-slave-backup option

Reported by Lachlan Mulcahy on 2011-09-27
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

When using --safe-slave-backup option innobackupex will correctly detect whether or not the host is a slave in the wait_for_safe_slave() function and not attempt to STOP/START slave, however, the script will still attempt to restart the slave later on. If the host is not a slave, this will cause innobackupex to exit with non-zero exit code, despite the issue being benign.

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

Other bug subscribers