Slave thread should be restarted when innobackupex fails

Bug #1248835 reported by Alexey Kopytov on 2013-11-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Medium
Unassigned
2.1
Medium
Unassigned
2.2
Medium
Unassigned
2.3
Medium
Unassigned

Bug Description

This is similar to bug #1037379. innobackupex should also make sure that the slave SQL thread is restarted if it fails with an error between STOP SLAVE SQL_THREAD and START SLAVE SQL_THREAD, i.e. when --safe-slave-backup is used.

Jaime Sicam (jssicam) on 2014-02-02
tags: added: percona-36549
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers