Slave thread should be restarted when innobackupex fails
Bug #1248835 reported by
Alexey Kopytov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Triaged
|
Medium
|
Unassigned | ||
| 2.1 |
Triaged
|
Medium
|
Unassigned | ||
| 2.2 |
Triaged
|
Medium
|
Unassigned | ||
| 2.3 |
Triaged
|
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.
| tags: | added: percona-36549 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/