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

Unexpected ER_LOCK_DEADLOCK upon BACKUP STAGE BLOCK_COMMIT

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.4(EOL)
    • 10.4(EOL)
    • Backup, Locking
    • None

    Description

      Note: The test case currently fails for me every time, but it's still a race condition, so it can vary on different machines and builds. Run with --repeat=N if it doesn't fail right away. We can also convert it into a concurrent test if necessary.

      CREATE TABLE t1 (a INT) ENGINE=MyISAM;
       
      --connect (con1,localhost,root,,test)
      BACKUP STAGE START;
      --send
        BACKUP STAGE BLOCK_COMMIT;
       
      --connection default
      SET lock_wait_timeout= 1;
      --error ER_LOCK_WAIT_TIMEOUT
      ALTER TABLE t1 ADD INDEX (a);
       
      --connection con1
      --reap
       
      # Cleanup
      --disconnect con1
      --connection default
      DROP TABLE t1;
      

      10.4 301bd62b253

      mysqltest: At line 14: query 'reap' failed: 1213: Deadlock found when trying to get lock; try restarting transaction
      

      The most important effect is that MariaBackup backup might fail with the deadlock error.

      Attachments

        Issue Links

          Activity

            There are no comments yet on this issue.

            People

              monty Michael Widenius
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.