Print locking transaction which cause "Lock wait timeout" errors into log file
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
||||
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Won't Fix
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Wishlist
|
Vlad Lesin | |||
5.7 |
Fix Released
|
Wishlist
|
Vlad Lesin |
Bug Description
Description:
Currently InnoDB has option innodb_
Since blocking transaction is often multiple statement transaction, if possible, print all statements. You may print all statements depending if historical Performance Schema instrumentation for statements enabled or not: in this case server already stored statements, participated in the transaction.
How to repeat:
Ask your colleague to run high concurrent load which produces "Lock wait timeout" errors, try to find reason for them.
TokuDB can do this if option tokudb_
The implementation without audit plugin can be found here:
https:/ /github. com/percona/ percona- server/ pull/1970 /github. com/percona/ percona- server/ pull/1971
https:/