innobackupex --slave-info doesn't handle slave_parallel_workers>0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Alexey Kopytov | ||
2.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.2 |
Fix Released
|
Medium
|
Alexey Kopytov | ||
2.3 |
Fix Released
|
Medium
|
Alexey Kopytov |
Bug Description
From http://
"When using a multi-threaded slave (by setting slave_parallel_
So, it is not safe to rely on Exec_Master_Log_Pos for "latest executed position in master binary log" if parallel replication is used, i.e. slave_parallel_
innobackupex should refuse to allow the use of the --slave-info option if slave_parallel_
A new option to innobackupex could be offered that would execute a sequence such as this:
SET @old_slave_
SET GLOBAL slave_parallel_
STOP SLAVE;
START SLAVE;
...execute backup logic...
SET GLOBAL slave_parallel_
STOP SLAVE;
START SLAVE;
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 151 lines (+93/-9)2 files modifiedstorage/innobase/xtrabackup/innobackupex.pl (+39/-9)
storage/innobase/xtrabackup/test/t/bug1372679.sh (+54/-0)
I have tried to check it with slave_parallel_ workers= 4 and yes, backup silently starts without warnings and this is a problem.
Either it should not allow to use --slave-info OR we can use above sequence to take backup.