pt-deadlock-logger can't clear deadlocks on 5.5

Bug #941064 reported by Baron Schwartz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Fix Released
Medium
Baron Schwartz

Bug Description

It hangs forever, and I see this in SHOW ENGINE INNODB STATUS:

---TRANSACTION 2900, not started
MySQL thread id 44, OS thread handle 0xaf0f1b90, query id 1452 localhost 127.0.0.1 msandbox Waiting for table metadata lock
DROP TABLE test.make_deadlock
---TRANSACTION 28FF, ACTIVE 2184 sec
3 lock struct(s), heap size 320, 2 row lock(s), undo log entries 2
MySQL thread id 43, OS thread handle 0xaf05eb90, query id 1451 localhost msandbox

Meanwhile, in processlist:

*************************** 4. row ***************************
     Id: 43
   User: msandbox
   Host: localhost
     db: test
Command: Sleep
   Time: 2263
  State:
   Info: NULL
*************************** 5. row ***************************
     Id: 44
   User: msandbox
   Host: localhost:39804
     db: test
Command: Query
   Time: 2263
  State: Waiting for table metadata lock
   Info: DROP TABLE test.make_deadlock

Revision history for this message
Baron Schwartz (baron-xaprb) wrote :

Killing connection 43 above makes it go ahead.

tags: added: mysql-5.5
Changed in percona-toolkit:
status: New → Confirmed
Revision history for this message
Baron Schwartz (baron-xaprb) wrote :

This makes the test suite fail on 5.5 in pt-deadlock-logger/standard_options. It also fails "badly" by hanging forever.

Changed in percona-toolkit:
importance: Undecided → Medium
Brian Fraser (fraserbn)
Changed in percona-toolkit:
milestone: none → 2.1.2
status: Confirmed → Fix Committed
Changed in percona-toolkit:
assignee: nobody → Baron Schwartz (baron-xaprb)
Changed in percona-toolkit:
status: Fix Committed → Fix Released
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-485

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.