[MDEV-8777] Adding constraint on InnoDB-Table locks whole database, although an index for that constraint already exists Created: 2015-09-09 Updated: 2015-11-16 Resolved: 2015-11-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Locking, Storage Engine - InnoDB |
| Affects Version/s: | 10.0.21-galera |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Uwe Beierlein | Assignee: | Nirbhay Choubey (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Description |
|
We are running a Galera-Cluster with 3 Nodes. Someone accidently deleted all foreign-keys of a table. The corresponding Index-Entries remained. Because the Index-Entry did exist we assumed that we can alter the table to add one of the missing foreign-keys using "total order isolation" without a global lock. But the database was locked for hours. It would be nice, if creation of foreign-keys would not block the whole database when an corresponding index already exists. |
| Comments |
| Comment by Sergei Golubchik [ 2015-11-01 ] |
|
What MariaDB version are you using? |
| Comment by Uwe Beierlein [ 2015-11-02 ] |
|
It was the most recent 10.0.x-galera - version |
| Comment by Nirbhay Choubey (Inactive) [ 2015-11-16 ] |
|
Duplicate of |