Issue with THD::awake and ha_kill_connection

Bug #1233690 reported by Raghavendra D Prabhu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Expired
Undecided
Unassigned
5.5
Expired
Undecided
Unassigned
5.6
Expired
Undecided
Unassigned

Bug Description

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.

description: updated
Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

If this is still relevant for Percona Server, do you have any idea of a test case to run to confirm this?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona Server because there has been no activity for 60 days.]

Changed in percona-server:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona Server 5.6 because there has been no activity for 60 days.]

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona Server 5.5 because there has been no activity for 60 days.]

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/PS-3037

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers