Uploaded image for project: 'Percona Server'
  1. Percona Server
  2. PS-255

lp1657737 - Print locking transaction which cause "Lock wait timeout" errors into log file

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Done
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 5.7.19-17, 5.6.37-82.2
    • Fix Version/s: 5.7.20-18, 5.6.38-83.0
    • Component/s: None
    • Labels:
      None

      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.

      TokuDB can do this if option tokudb_lock_timeout_debug is set

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                vladislav.lesin Vladislav Lesin
                Reporter:
                david.bennett David Bennett
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: