Handler command and concurrent DDL can cause node hanging
Bug #1233353 reported by
Seppo Jaakola
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| MySQL patches by Codership | Status tracked in 5.6 | |||||
| 5.5 |
Fix Released
|
Low
|
Seppo Jaakola | |||
| 5.6 |
Fix Released
|
Low
|
Seppo Jaakola | |||
| Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
| 5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
| 5.6 |
Fix Released
|
Undecided
|
Unassigned | |||
Bug Description
Table handler session can enter into unresolved MDL lock wait with a replicated DDL statement.
The problem happens when a handler session is aborted due to replication conflict. The wsrep abort handler does not release exclusive MDL lock, which remains effective for following sessions. If the connection issues DDL statement as next step, there can be MDL conflict between this DDL and some other replicated DDL.
To reproduce, start two nodes and run two sessions of randgen handler.yy tests against separate nodes.
| Changed in codership-mysql: | |
| status: | New → In Progress |
| importance: | Undecided → Low |
| assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
| milestone: | none → 5.5.34-24.9 |
| no longer affects: | codership-mysql/5.5 |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #1 |
| Changed in codership-mysql: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
Fix pushed in wsrep-5.5-23 in revision: http://
Fix pushed in wsrep-5.5 in revision: http://
Fix pushed in wsrep-5.6 in revision: http://