innodb_thread_conccurrency limit can cause node stalling

Bug #1155183 reported by Seppo Jaakola
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Fix Released
Medium
Seppo Jaakola
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Fix Released
Undecided
Unassigned

Bug Description

If innodb_thread_concurrency has been defined to throttle innodb access, and work load contains DDL statements, a cluster node can remain hanging for unresolved MDL conflict.

Changed in codership-mysql:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Seppo Jaakola (seppo-jaakola)
milestone: none → 5.5.30-23.7.4
Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

Fix pushed in: http://bazaar.launchpad.net/~codership/codership-mysql/5.5-23/revision/3856

The fix adds new method to cancel a thread waiting for innodb concurrency

Changed in codership-mysql:
status: In Progress → Fix Committed
Changed in percona-xtradb-cluster:
milestone: none → 5.5.30-23.7.4
status: New → Fix Released
Changed in codership-mysql:
status: Fix Committed → Fix Released
Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

The fix for this looks already ported.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1314

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.