Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
Description
The same test case passes with xtrabackup 2.4.5 and fails in current 10.1.22 (UPDATE 4-Apr-17 : the test passes with 2.3.6 and 2.3.7 as well)
Needs investigation and may be converted to bug as I am not sure what priority should be and if this is really unexpected behavior or just different implementation of place where sync point is created.
Attachments
Issue Links
- is part of
-
MDEV-16791 mariabackup : allow consistent backup, in presence of concurrent DDL, also without --lock-ddl-per-table
- Closed
- relates to
-
MDEV-14095 Concurrent DDL can break xtrabackup-v2 SST in 10.2
- Closed