Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-4395

Documentation mentions 2-step deadlock detection

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.5.30
    • Fix Version/s: None
    • Component/s: None

      Description

      https://kb.askmonty.org/en/mysqld-options-full-list/ - MariaDB options page that shows the 2-step deadlock variables:

      deadlock-search-depth-short is a number for the short search depth for the two-step deadlock detection, deadlock-timeout-long is a number of the long timeout for the two-step deadlock detection, in microseconds, and the deadlock-timeout-short is a number of the long timeout for the two-step deadlock detection, in microseconds

      These 4 variables are not used in InnoDB at all, according to serg. There's no documentation on how they're used in Aria. The docs should be more verbose about these options, how the 2-step detection should work, and where it works and doesn't.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            serg Sergei Golubchik added a comment -

            I've added a note that these variables only apply to the Aria engine

            Show
            serg Sergei Golubchik added a comment - I've added a note that these variables only apply to the Aria engine
            Show
            greenman Ian Gilfillan added a comment - Documented now at https://kb.askmonty.org/en/aria-two-step-deadlock-detection/
            Hide
            dbart Daniel Bartholomew added a comment -

            documentation fixed, so closing

            Show
            dbart Daniel Bartholomew added a comment - documentation fixed, so closing

              People

              • Assignee:
                dbart Daniel Bartholomew
                Reporter:
                Sheeri Sheeri Cabral
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 30 minutes
                  30m