Bug #69338 Improved diagnostics for metadata locking deadlocks
Submitted: 28 May 2013 21:29 Modified: 29 May 2013 5:53
Reporter: Dmitry Lenev Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Locking Severity:S4 (Feature request)
Version:5.7.2 OS:Any
Assigned to: CPU Architecture:Any

[28 May 2013 21:29] Dmitry Lenev
Metadata locking subsystem can be improved:

 - By having an option for logging all metadata locking deadlocks to error log,
   similar to option --innodb_print_all_deadlocks.
 - Adding status variable (or even several variables) for number of metadata
   locking deadlocks which has occurred.

How to repeat:
Reproduce metadata locking deadlock, see no message in error log and no status variable change.
[28 May 2013 21:31] Dmitry Lenev
See also bug #65890 "Deadlock that is not a deadlock with transaction and lock tables" for some rationale for these features.