Bug #84563 Print locking transaction which cause "Lock wait timeout" errors into log file

• Submitted: 19 Jan 2017 12:58
• Modified: 21 Jan 2017 8:02
• Reporter: Sveta Smirnova (OCA)
• Status: Verified
• Category: MySQL Server: InnoDB storage engine
• Severity: S4 (Feature request)
• Version: 5.5, 5.6, 5.7, 8.0
• OS: Any
• CPU Architecture: Any

[19 Jan 2017 12:58] Sveta Smirnova

Description:
Currently InnoDB has option innodb_print_all_deadlocks which tells InnoDB to redirect information about all deadlocks into log file. Please implement similar feature, but for "Lock wait timeout" errors. Print information about both failed and blocking transactions.

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.

[21 Jan 2017 8:02] MySQL Verification Team

Hello Sveta,

Thank you for the feature request!

Thanks,
Umesh