unresolved MDL deadlock with limited innodb thread concurrency

Bug #861212 reported by Seppo Jaakola
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Fix Released
High
Seppo Jaakola
5.5
Fix Released
High
Seppo Jaakola

Bug Description

Hanging happens in 1.0beta evaluation with following use case:

* innodb_thread_concurrency=32
* ~50 client connections running short autocommit queries
  (UPDATE,DELETE,INSERT)
* one UPDATE with INNER JOIN, updating 'queue' table
* one DDL running: CREATE TABLE IF NOT EXISTS queue(...)

The DDL stays hanging in state: "Waiting for table metadata lock", killing this query resolves the deadlock.

Related branches

description: updated
summary: - unresolved MDL conflict with limited innodb thread concurrency
+ unresolved MDL deadlock with limited innodb thread concurrency
Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

development head has a number of fixes for DDL processing with respect to MDL usage. These fixes mostly dealt with issues found with FTWRL..
Change set 3567 adds one more fix for this: now BF thread can use wsrep_abort_thd() to kill local state MDL victim.

Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

Hanging happens with 2.0 RC, with following regression test:

sqlgen --host gw --port 3307 --users 12 --create 1 --duration 3600 --rows 1000 --ac-frac 10 --rollbacks 0.1 --alters 0.001

and cluster topology: 2 nodes MM load balanced

Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.