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

GCF-1060 test causes a server crash

Details

    Description

      The server crashes with:

      2023-12-28 17:29:32 89 [Note] WSREP: ::rollback() thread: 89, client_state exec client_mode high priority trans_state aborted killed 0
      		 
      2023-12-28 17:29:32 76 [Note] WSREP: MDL conflict·
      		 
      schema:  test
      		 
      request: (75    seqno 626   wsrep (toi, exec, aborted) cmd 3 8  TRUNCATE TABLE t1)
      		 
      granted: (89    seqno -1    wsrep (high priority, exec, aborting) cmd 0 161     (null))
      		 
      2023-12-28 17:29:32 76 [Note] WSREP: MDL ticket: type: MDL_SHARED_WRITE space: TABLE db: test name: t1 (Waiting for table metadata lock)
      		 
      2023-12-28 17:29:32 76 [Note] WSREP: MDL BF-BF conflict
      		 
      schema:  test
      		 
      request: (75    seqno 626   wsrep (toi, exec, aborted) cmd 3 8  TRUNCATE TABLE t1)
      		 
      granted: (89    seqno -1    wsrep (high priority, exec, aborted) cmd 0 161  (null))
      		 
      2023-12-28 17:29:32 76 [Note] WSREP: MDL ticket: type: MDL_SHARED_WRITE space: TABLE db: test name: t1 (Waiting for table metadata lock)
      		 
      2023-12-28 17:29:32 76 [ERROR] Aborting

      The problem is as following:
      Applied SR transaction gets BF-aborted, but there is a time window when it's already rolled back and its wsrep transaction's state is set to aborted, but it has not released MDL locks yet. This situation is incorrectly determined during MDL conflict handling and the server aborts thinking there are two high-priority transactions (TOI and high-prio applied) conflicting, which should never happen.

      Attachments

        1. mysqld.2.err
          1.09 MB
        2. mysqld.1.err
          1.13 MB

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32160 GCF-1060 test failure due to wsrep MDL conflict

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

          Activity

            sysprg Julius Goryavsky added a comment -

            Fixes have been merged with head revision: https://github.com/MariaDB/server/commit/235f33e3606b79c5e3b75f4cfd1ca6d92320e9a2 and as part of https://github.com/MariaDB/server/commit/d5a669b6b645926360c2a36a99d14501fe8c91fa

            sysprg Julius Goryavsky added a comment - Fixes have been merged with head revision: https://github.com/MariaDB/server/commit/235f33e3606b79c5e3b75f4cfd1ca6d92320e9a2 and as part of https://github.com/MariaDB/server/commit/d5a669b6b645926360c2a36a99d14501fe8c91fa

            People

              sysprg Julius Goryavsky
              denis.protivensky Denis Protivensky
              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.