Make --lock-ddl and --lock-ddl-per-table mutually exclusive
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.4 |
Triaged
|
Medium
|
Sergei Glushchenko |
Bug Description
If you use both --lock-ddl and --lock-
xtrabackup --defaults-
show processlist;
+-----+
| Id | User | Host | db | Command | Time | State | Info | Rows_sent | Rows_examined |
+-----+
| 7 | root | localhost | NULL | Query | 0 | starting | show processlist | 0 | 0 |
| 225 | msandbox | localhost:46153 | NULL | Sleep | 177 | | NULL | 1 | 116 |
| 226 | root | localhost | NULL | Query | 176 | Waiting for backup lock | drop table if exists db2.sb1 | 0 | 0 |
| 227 | msandbox | localhost:46154 | NULL | Query | 175 | Waiting for table metadata lock | SELECT * FROM db2.sb1 LIMIT 1 | 0 | 0 |
+-----+
4 rows in set (0.00 sec)
The best is to make these options to be mutually exclusive.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PXB-792