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

innodb.deadlock_victim_race is unstable

Details

    Description

      innodb.deadlock_victim_race 'innodb'     w3 [ fail ]
      		 
              Test ended at 2022-09-01 13:58:59
      		 
       
      		 
      CURRENT_TEST: innodb.deadlock_victim_race
      		 
      mysqltest: At line 79: query 'SELECT * FROM t WHERE a = 10 FOR UPDATE' succeeded - should have failed with error ER_LOCK_WAIT_TIMEOUT (1205)...

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29081 trx_t::lock.was_chosen_as_deadlock_victim race in lock_wait_end()

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

          Activity

            vlad.lesin Vladislav Lesin added a comment -

            The instability can be repeated with the following script:

            #!/bin/bash                                                                     
                                                                                            
            runOutputScript() {                                                             
              local num=$1                                                                  
              echo "Running output script: ${num}"                                          
                ./mtr --force --max-test-fail=1 --suite-timeout=999999999 --testcase-timeout=99999999 --parallel=1 --debug-sync-timeout=30 --repeat=1000 --vardir=$PWD/var-$num innodb.deadlock_victim_race > $PWD/out-$num 2>&1
            		 
            }                                                                               
                                                                                            
            trap "exit" INT TERM ERR                                                        
            trap "kill 0" EXIT                                                              
                                                                                            
            i=300                                                                           
            while [ $i -ne 0 ];                                                             
            do                                                                              
              runOutputScript $i &                                                          
              i=$[$i-1]                                                                     
            done                                                                            
                                                                                            
            wait

            As we can't develop test for test, the above script can be used to check if the fix works.

            vlad.lesin Vladislav Lesin added a comment - The instability can be repeated with the following script: #!/bin/bash runOutputScript() { local num=$ 1 echo "Running output script: ${num}" ./mtr --force --max-test-fail= 1 --suite-timeout= 999999999 --testcase-timeout= 99999999 --parallel= 1 --debug-sync-timeout= 30 --repeat= 1000 --vardir=$PWD/var-$num innodb.deadlock_victim_race > $PWD/out-$num 2 >& 1 } trap "exit" INT TERM ERR trap "kill 0" EXIT i= 300 while [ $i -ne 0 ]; do runOutputScript $i & i=$[$i- 1 ] done wait As we can't develop test for test, the above script can be used to check if the fix works.

            People

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