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

Deadlock failure that does not occur elsewhere

Details

    Description

      MariaDB gets the following deadlock error:

      localhost-dir: sql_create.c:837-5 Fill File table Query failed: INSERT INTO File
      (FileIndex, JobId, PathId, FilenameId, LStat, MD5, DeltaSeq) SELECT
      batch.FileIndex, batch.JobId, Path.PathId, Filename.FilenameId,batch.LStat,
      batch.MD5, batch.DeltaSeq FROM batch JOIN Path ON (batch.Path = Path.Path) JOIN
      Filename ON (batch.Name = Filename.Name): ERR=Deadlock found when trying to get
      lock;

      When running the Bacula 9.0.1 regression script named: three-pool-virtual-test
      This does not occur on any version of MySQL, nor the Ubuntu version 10.0 of MariaDB. The code has been stable for many years.

      I am running all instances of MariaDB and MySQL out of the box. I have changed no parameters.

      This appears to be a false deadlock detection. Note, it is 100% reproducible.

      Attachments

        1. mariadb-bug
          1 kB
        2. mdev13333.test
          2 kB
        3. output_b
          6.44 MB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-16067 Invalid deadlock detection

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-16709 InnoDB: Error: trx already had an AUTO-INC lock

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17561 Deadlocks happen often when updating different rows

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11080 InnoDB: Failing assertion: table->n_waiting_or_granted_auto_inc_locks > 0

          • Major - Major loss of function.
          • Closed

          Activity

            Descending order - Click to sort in ascending order
            marko Marko Mäkelä added a comment -

            This bug was independently introduced in MariaDB 10.2.2 when applying changes from MySQL 5.7.9.

            In MariaDB 10.1, the logic was only broken between MariaDB 10.1.32 and 10.1.35 (inclusive).

            marko Marko Mäkelä added a comment - This bug was independently introduced in MariaDB 10.2.2 when applying changes from MySQL 5.7.9 . In MariaDB 10.1, the logic was only broken between MariaDB 10.1.32 and 10.1.35 (inclusive).
            marko Marko Mäkelä added a comment -

            I believe that this may have been caused by my code clean-up in 10.1. I got confused by the many WSREP-related predicates in the code.

            marko Marko Mäkelä added a comment - I believe that this may have been caused by my code clean-up in 10.1. I got confused by the many WSREP-related predicates in the code.
            serg Sergei Golubchik added a comment -

            I've just checked, 10.1.36 is on the roadmap with the release date 2018-09-14

            serg Sergei Golubchik added a comment - I've just checked, 10.1.36 is on the roadmap with the release date 2018-09-14
            azurit azurit added a comment -

            What's the release date of 10.1.36? I can see only 10.1.35 in the road map and it was supposed to be released on 2018-07-27. Thank you.

            azurit azurit added a comment - What's the release date of 10.1.36? I can see only 10.1.35 in the road map and it was supposed to be released on 2018-07-27. Thank you.
            azurit azurit added a comment -

            azurit azurit added a comment -
            View 24 older comments

            People

              jplindst Jan Lindström (Inactive)
              kern Kern Sibbald
              Votes:
              1 Vote for this issue
              Watchers:
              8 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.