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

Found wrong usage of mutex 'LOCK_thd_kill' and 'LOCK_wsrep_server_state

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 10.4
    • Fix Version/s: N/A
    • Component/s: Galera, Tests
    • Labels:
      None

      Description

       galera_sr.mysql-wsrep-features#27 (Failed 4 times in the last 30 runs. Flakiness: 24%, Stability: 86%)
       Stack Trace
      CREATE TABLE t1 (f1 INTEGER PRIMARY KEY) ENGINE=InnoDB;
      SET SESSION wsrep_trx_fragment_size = 1;
      SET AUTOCOMMIT=OFF;
      START TRANSACTION;
      INSERT INTO t1 VALUES (1);
      INSERT INTO t1 VALUES (2);
      INSERT INTO t1 VALUES (3);
      INSERT INTO t1 VALUES (4);
      INSERT INTO t1 VALUES (5);
      connect node_1a, 127.0.0.1, root, , test, $NODE_MYPORT_1;
      ALTER TABLE t1 ADD COLUMN f2 INTEGER;
      connection node_2;
      SET SESSION wsrep_sync_wait = 0;
      SELECT COUNT(*) = 0 FROM t1;
      COUNT(*) = 0
      1
      connection node_1;
      COMMIT;
      ERROR 40001: Deadlock found when trying to get lock; try restarting transaction
      DROP TABLE t1;
      line
      safe_mutex: Found wrong usage of mutex 'LOCK_thd_kill' and 'LOCK_wsrep_server_state'
      ^ Found warnings in /var/tmp/mtr/2/log/mysqld.1.err
      

        Attachments

          Activity

            People

            Assignee:
            sciascid Daniele Sciascia
            Reporter:
            jplindst Jan Lindström
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration