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: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.5(EOL), 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(EOL)
    • 11.4.5, 11.7.2
    • 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

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-39799 Assertion `!(wait_lock->is_insert_intention()) || (wait_lock->is_gap()) || is_supremum' failed

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-39800 Assertion `!(mode & 2048U) || (mode & 512U) || is_supremum' failed

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34652 Deadlock when upgrading shared lock to exclusive

          • Major - Major loss of function.
          • Closed
          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

          Task - A task that needs to be done. MDEV-35930 optimize lock_rec_find_set_bit() function

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-35931 optimize lock_rec_has_expl() to stop iteration when waiting lock is reached

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-35932 unify functions which are looking for conflicting record lock in locks queue

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18706 ER_LOCK_DEADLOCK on concurrent read and insert into already locked gap

          • Major - Major loss of function.
          • Stalled

          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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27992 DELETE fails to delete record after blocking is released

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

          SAMU-292 Loading...

          Activity

            People

              vlad.lesin Vladislav Lesin (Inactive)
              vlad.lesin Vladislav Lesin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 9.4d Original Estimate - 9.4d
                  9.4d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 46d 2.5h
                  46d 2.5h

                  Git Integration

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