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

Invalid deadlock detection

Details

    Description

      After upgrading from Debian Jessie to Debian Stretch using MariaDB 10.1.32 packages from mariadb.org, we immediately started having problems with our backup software, Bacula ( www.bacula.org ) - the backup jobs are failing with this error:
      Deadlock found when trying to get lock; try restarting transaction

      This is happening every night for different backup jobs (probably random) and has NEVER happened before. While upgrading Debian, there was only a minor version change of Bacula (7.4.3 to 7.4.4). From my observation, error is happening for randomly for same SQL commands, sometimes after 300 seconds, sometimes after 2000 seconds of execution/waiting for locks. This is happening even after i set this:
      innodb_lock_wait_timeout = 100000

      I also tried upgrading to 10.2.14 and set this:
      innodb_deadlock_detect = 0

      Which does nothing, problem persists.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13333 Deadlock failure that does not occur elsewhere

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 5 older comments
            alice Alice Sherepa added a comment -

            azurit, it looks like it is the same problem as MDEV-13333, so I suggest to wait for MDEV-13333 to be fixed.
            If the bug will be still reproducible, then it will be investigated further.

            alice Alice Sherepa added a comment - azurit , it looks like it is the same problem as MDEV-13333 , so I suggest to wait for MDEV-13333 to be fixed. If the bug will be still reproducible, then it will be investigated further.
            jplindst Jan Lindström (Inactive) added a comment -

            @azurit try set global innodb_lock_schedule_algorithm=FCFS;

            jplindst Jan Lindström (Inactive) added a comment - @azurit try set global innodb_lock_schedule_algorithm=FCFS;
            azurit azurit added a comment -

            I'm, currently, on 10.1 so it is already set to 'fcfs'. The problem is still occuring but it's not so often as on 10.2. Any suggestions how to bypass it on 10.1? It is really doing us lots of trouble.

            azurit azurit added a comment - I'm, currently, on 10.1 so it is already set to 'fcfs'. The problem is still occuring but it's not so often as on 10.2. Any suggestions how to bypass it on 10.1? It is really doing us lots of trouble.
            alice Alice Sherepa added a comment -

            azurit MDEV-13333 is fixed now, are you able to try 10.1.36 to confirm that the problem is solved?

            alice Alice Sherepa added a comment - azurit MDEV-13333 is fixed now, are you able to try 10.1.36 to confirm that the problem is solved?
            azurit azurit added a comment -

            I cannot tell for 100%, because the problem was appearing randomly, but it looks good so far. Thank you!

            azurit azurit added a comment - I cannot tell for 100%, because the problem was appearing randomly, but it looks good so far. Thank you!

            People

              alice Alice Sherepa
              azurit azurit
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.