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

mtr failure: innodb.deadlock_wait_thr_race

Details

    Description

      mtr failure:

       
      CURRENT_TEST: innodb.deadlock_wait_thr_race
      mysqltest: At line 61: query 'reap' failed: ER_LOCK_WAIT_TIMEOUT (1205): Lock wait timeout exceeded; try restarting transaction
       
      The result from queries just before the failure was:
      < snip >
      SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
      SET DEBUG_SYNC = 'lock_trx_handle_wait_enter SIGNAL upd_locked WAIT_FOR upd_cont';
      SET DEBUG_SYNC = 'trx_t_release_locks_enter SIGNAL sel_cont WAIT_FOR upd_cont_2';
      BEGIN;
      UPDATE t SET b = 100;
      connection default;
      SET DEBUG_SYNC="now WAIT_FOR upd_locked";
      SET DEBUG_SYNC="deadlock_report_before_lock_releasing SIGNAL upd_cont WAIT_FOR sel_cont";
      SET DEBUG_SYNC="lock_wait_before_suspend SIGNAL sel_before_suspend";
      SELECT * FROM t WHERE a = 10 FOR UPDATE;;
      connect con_3,localhost,root,,;
      SET DEBUG_SYNC="now WAIT_FOR sel_before_suspend";
      Warnings:
      Warning	1639	debug sync point wait timed out
      SET DEBUG_SYNC="now SIGNAL upd_cont_2";
      disconnect con_3;
      connection con_2;
      ERROR 40001: Deadlock found when trying to get lock; try restarting transaction
      disconnect con_2;
      connection default;
       
      More results from queries before failure can be found in D:\Buildbot\amd64-windows\build\mysql-test\var\12\log\deadlock_wait_thr_race.log
      

      Attachments

        Issue Links

          Activity

            danblack Daniel Black created issue -
            danblack Daniel Black made changes -
            Field Original Value New Value
            marko Marko Mäkelä made changes -
            Summary mtr failure: innodb.deadlock_wait_thr_rac mtr failure: innodb.deadlock_wait_thr_race

            Also the test innodb.deadlock_wait_lock_race would easily hang on my Debian GNU/Linux system when I run ./mtr --parallel=60 --big-test --force. On this system, nproc reports 40 (hyper)threads.

            The amd64-windows builder has very many CPU cores. There could be some race condition in the test. On a system with significantly fewer cores, perhaps running with innodb_purge_threads=1 would improve reproducibility?

            marko Marko Mäkelä added a comment - Also the test innodb.deadlock_wait_lock_race would easily hang on my Debian GNU/Linux system when I run ./mtr --parallel=60 --big-test --force . On this system, nproc reports 40 (hyper)threads. The amd64-windows builder has very many CPU cores. There could be some race condition in the test. On a system with significantly fewer cores, perhaps running with innodb_purge_threads=1 would improve reproducibility?
            julien.fritsch Julien Fritsch made changes -
            Priority Blocker [ 1 ] Critical [ 2 ]
            marko Marko Mäkelä made changes -
            Fix Version/s 10.6.11 [ 28441 ]
            Fix Version/s 10.7.7 [ 28442 ]
            Fix Version/s 10.8.6 [ 28443 ]
            Fix Version/s 10.9.4 [ 28444 ]
            Fix Version/s 10.10.2 [ 28410 ]
            Fix Version/s 10.11.1 [ 28454 ]
            Fix Version/s 10.6 [ 24028 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            marko Marko Mäkelä made changes -

            People

              vlad.lesin Vladislav Lesin
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.