Percona Server moved to https://jira.percona.com/projects/PS

  1. Bug #1233690
  2. Comment #0

Comment 0 for bug 1233690

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

After porting of twitter's timeout patch in
https://blueprints.launchpad.net/percona-server/+spec/port-max-statement
-time, it is possible for deadlock to occur when THD::awake is
invoked from within innodb itself. One is the case presented
here: https://bugs.launchpad.net/percona-xtradb-cluster/5.6/+bug/1233301
where the wsrep code calls THD::awake during a BF abort and deadlocks
on lock_sys->mutex and trx->mutex. It is better to fix this in innodb
itself since otherwise it may require changes outside it.

This affects both 5.5 and 5.6 trees.