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

Port "Bug #11745929 Change lock priority so that the transaction holding S-lock gets X-lock first" fix from MySQL to MariaDB

    XMLWordPrintable

Details

    • Bug
    • Status: In Progress (View Workflow)
    • Critical
    • Resolution: Unresolved
    • 10.5, 10.6, 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL), 11.4, 11.5(EOL), 11.6(EOL), 11.7
    • 10.5, 10.6, 10.11, 11.4, 11.7
    • Storage Engine - InnoDB

    Description

      MDEV-27025 describes the following case:
      1. trx1 gets an S-lock granted
      2. trx2 wants an X-lock, but has to wait for trx1
      3. trx1 now wants an X-lock, but waits for trx2

      The try to fix MDEV-27025 caused MDEV-27992, what made us to revert MDEV-27025 fix(see also this comment). It seems, MySQL's "Bug #11745929" fix solves MDEV-27025 issue.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35624 Innodb: Avoid Implicit Lock check when the lock queue is not empty

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27025 insert-intention lock conflicts with waiting ORDINARY lock

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              vlad.lesin Vladislav Lesin
              vlad.lesin Vladislav Lesin
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.