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

Bug #860879 reported by Lachlan Mulcahy
6
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

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.

Related branches

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1131

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.