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

After upgrade to 10.11.12 we see significant higher InnoDB locking

    XMLWordPrintable

Details

    Description

      We upgraded this morning at 08:44 from MariaDB 10.11.11 to 10.11.12 which was released on 6 May.

      At 11:37 we were notice by customer that his application server is causing troubles. See Graph 1.

      At 12:09 customer notices us, that query looks like this:

      UPDATE <table_name> SET w1 = 200, w2 = 5, w3 = 2 where w1=0 AND w2 = 0 AND w3 = 0
      [2025-05-08 12:05:25] [HY000][1205] (conn=2696579) Lock wait timeout exceeded; try restarting transaction

      We see similar reactions on our InnoDB monitoring. See Graf 2.

      This also could seriously affect other customers IMHO.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-36759 huge performance drop after update

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-36759 huge performance drop after update

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-36772 After update from 10.11.11 to 10.11.12 thousand times slower

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

          Activity

            People

              marko Marko Mäkelä
              oli Oli Sennhauser
              Votes:
              3 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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