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

Spurious deadlock error when wsrep_on=OFF

Details

    Description

      connection node_1;
      		 
      SET SESSION wsrep_on=OFF;
      		 
      BEGIN;
      		 
      ROLLBACK;
      		 
      SET SESSION wsrep_on=OFF;
      		 
      galera.t 'innodb'                        [ fail ]
      		 
              Test ended at 2024-02-22 09:58:51
      		 
       
      		 
      CURRENT_TEST: galera.t
      		 
      mysqltest: At line 6: query 'SET SESSION wsrep_on=OFF' failed: 1213: Deadlock found when trying to get lock; try restarting transaction

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          sciascid Daniele Sciascia created issue -
          sciascid Daniele Sciascia made changes -
          Field Original Value New Value
          Assignee Daniele Sciascia [ sciascid ]
          sysprg Julius Goryavsky made changes -
          Assignee Daniele Sciascia [ sciascid ] Julius Goryavsky [ sysprg ]
          sysprg Julius Goryavsky made changes -
          Priority Minor [ 4 ] Major [ 3 ]
          sysprg Julius Goryavsky made changes -
          Fix Version/s 10.5.26 [ 29832 ]
          Fix Version/s 10.4 [ 22408 ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          JIraAutomate JiraAutomate made changes -
          Fix Version/s 10.6.19 [ 29833 ]
          Fix Version/s 10.11.9 [ 29834 ]
          Fix Version/s 11.1.6 [ 29835 ]
          Fix Version/s 11.2.5 [ 29836 ]
          Fix Version/s 11.4.3 [ 29837 ]

          People

            sysprg Julius Goryavsky
            sciascid Daniele Sciascia
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.