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

Bug #1064482 reported by Michael Coburn
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Won't Fix
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;

Tags: pt-stalk
Brian Fraser (fraserbn)
Changed in percona-toolkit:
status: New → Confirmed
tags: added: pt-stalk
Revision history for this message
Sveta Smirnova (svetasmirnova) wrote :

This feature included into latest versions

Revision history for this message
Carlos Salguero (carlos-salguero) wrote :

It is already included in 2.2.19

Changed in percona-toolkit:
status: Confirmed → Won't Fix
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/PT-1036

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.