include collection of InnoDB locks and transactions as part of pt-stalk

Reported by Michael Coburn on 2012-10-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit
Undecided
Unassigned

Bug Description

It would be interesting to identify which transaction is blocking another when performing a pt-stalk collection.

Resources:

http://dev.mysql.com/doc/innodb/1.1/en/innodb-information-schema-examples.html

SELECT r.trx_id waiting_trx_id,
       r.trx_mysql_thread_id waiting_thread,
       r.trx_query waiting_query,
       b.trx_id blocking_trx_id,
       b.trx_mysql_thread_id blocking_thread,
       b.trx_query blocking_query
   FROM information_schema.innodb_lock_waits w
   INNER JOIN information_schema.innodb_trx b ON
    b.trx_id = w.blocking_trx_id
  INNER JOIN information_schema.innodb_trx r ON
    r.trx_id = w.requesting_trx_id;

Brian Fraser (fraserbn) on 2012-10-10
Changed in percona-toolkit:
status: New → Confirmed
tags: added: pt-stalk
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers