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

Concurrent UPDATE and DROP TABLE cause MDL BF-BF conflict

Details

    Description

      DROP TABLE of child may apply concurrently with UPDATE parent table. It appears that DROP TABLE does not append certification key for parent table, even though it takes MDL lock on the parent (thus causing the BF-BF conflict).

      2024-09-26 15:45:15 2 [Note] WSREP: MDL BF-BF conflict
      schema:  test
      request: (2     seqno 9         wsrep (toi, exec, executing) cmd 0 9    DROP TABLE t2)
      granted: (11    seqno 10        wsrep (high priority, exec, committing) cmd 0 161       (null))
      

      Attachments

        Activity

          sciascid Daniele Sciascia created issue -
          sciascid Daniele Sciascia made changes -
          Field Original Value New Value
          Description DROP TABLE of child may apply concurrently with UPDATE parent table. It appears that DROP TABLE does not append certification key for parent table, even though it takes MDL lock on the parent (thus causing the BF-BF conflict).

          {code}
          2024-09-26 15:45:15 2 [Note] WSREP: MDL BF-BF conflict
          schema: test
          request: (2 seqno 9 wsrep (toi, exec, executing) cmd 0 9 DROP TABLE t2)
          granted: (11 seqno 10 wsrep (high priority, exec, committing) cmd 0 161 (n
          ull))

          {code}
          DROP TABLE of child may apply concurrently with UPDATE parent table. It appears that DROP TABLE does not append certification key for parent table, even though it takes MDL lock on the parent (thus causing the BF-BF conflict).

          {code}
          2024-09-26 15:45:15 2 [Note] WSREP: MDL BF-BF conflict
          schema: test
          request: (2 seqno 9 wsrep (toi, exec, executing) cmd 0 9 DROP TABLE t2)
          granted: (11 seqno 10 wsrep (high priority, exec, committing) cmd 0 161 (null))
          {code}
          sciascid Daniele Sciascia made changes -
          Fix Version/s 10.5.27 [ 29902 ]
          sciascid Daniele Sciascia made changes -
          Affects Version/s 10.5.26 [ 29832 ]
          sciascid Daniele Sciascia made changes -
          Affects Version/s 10.5 [ 23123 ]
          Affects Version/s 10.5.26 [ 29832 ]
          sciascid Daniele Sciascia made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          serg Sergei Golubchik made changes -
          Fix Version/s 10.5 [ 23123 ]
          Fix Version/s 10.5.27 [ 29902 ]
          sciascid Daniele Sciascia made changes -
          Assignee Daniele Sciascia [ sciascid ] Julius Goryavsky [ sysprg ]
          Status In Progress [ 3 ] In Review [ 10002 ]
          sciascid Daniele Sciascia made changes -
          Priority Major [ 3 ] Critical [ 2 ]
          sysprg Julius Goryavsky made changes -
          Assignee Julius Goryavsky [ sysprg ] Daniele Sciascia [ sciascid ]
          sciascid Daniele Sciascia made changes -
          Assignee Daniele Sciascia [ sciascid ] Julius Goryavsky [ sysprg ]
          sysprg Julius Goryavsky made changes -
          Status In Review [ 10002 ] Stalled [ 10000 ]
          sysprg Julius Goryavsky made changes -
          Status Stalled [ 10000 ] In Progress [ 3 ]
          sysprg Julius Goryavsky made changes -
          Fix Version/s 10.5.28 [ 29952 ]
          Fix Version/s 10.5 [ 23123 ]
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Closed [ 6 ]
          JIraAutomate JiraAutomate made changes -
          Fix Version/s 10.6.21 [ 29953 ]
          Fix Version/s 10.11.11 [ 29954 ]
          Fix Version/s 11.4.5 [ 29956 ]
          Fix Version/s 11.7.2 [ 29914 ]

          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.