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

Assertion `(&(&thd->LOCK_thd_data)->m_mutex)->count > 0 && pthread_equal(pthread_self(), (&(&thd->LOCK_thd_data)->m_mutex)->thread)' failed in wsrep_thd_is_aborting with innodb_thread_concurrency=1

Details

    Description

      perl ./mtr galera.basic --mysqld=--innodb_thread_concurrency=1
      

      10.4 bdcecfa2

      mysqld: /data/src/10.4/sql/service_wsrep.cc:235: my_bool wsrep_thd_is_aborting(const THD*): Assertion `(&(&thd->LOCK_thd_data)->m_mutex)->count > 0 && pthread_equal(pthread_self(), (&(&thd->LOCK_thd_data)->m_mutex)->thread)' failed.
      200401 14:51:22 [ERROR] mysqld got signal 6 ;
       
      #7  0x00007f940f12cf12 in __GI___assert_fail (assertion=0x5588d084f710 "(&(&thd->LOCK_thd_data)->m_mutex)->count > 0 && pthread_equal(pthread_self(), (&(&thd->LOCK_thd_data)->m_mutex)->thread)", file=0x5588d084f5e8 "/data/src/10.4/sql/service_wsrep.cc", line=235, function=0x5588d084f8c0 <wsrep_thd_is_aborting::__PRETTY_FUNCTION__> "my_bool wsrep_thd_is_aborting(const THD*)") at assert.c:101
      #8  0x00005588cfd53122 in wsrep_thd_is_aborting (thd=0x7f9398000af0) at /data/src/10.4/sql/service_wsrep.cc:235
      #9  0x00005588d0290f6b in srv_conc_enter_innodb_with_atomics (trx=0x7f9400c57268) at /data/src/10.4/storage/innobase/srv/srv0conc.cc:122
      #10 0x00005588d02913c0 in srv_conc_enter_innodb (prebuilt=0x7f9398025b30) at /data/src/10.4/storage/innobase/srv/srv0conc.cc:234
      #11 0x00005588d006c31c in innobase_srv_conc_enter_innodb (prebuilt=0x7f9398025b30) at /data/src/10.4/storage/innobase/handler/ha_innodb.cc:1715
      #12 0x00005588d007a834 in ha_innobase::write_row (this=0x7f9398025338, record=0x7f939801e6d0 "\377\001") at /data/src/10.4/storage/innobase/handler/ha_innodb.cc:8045
      #13 0x00005588cfe3c59c in handler::ha_write_row (this=0x7f9398025338, buf=0x7f939801e6d0 "\377\001") at /data/src/10.4/sql/handler.cc:6677
      #14 0x00005588cfa81376 in write_record (thd=0x7f9398000af0, table=0x7f93980244d0, info=0x7f9400207000) at /data/src/10.4/sql/sql_insert.cc:2056
      #15 0x00005588cfa7e2e1 in mysql_insert (thd=0x7f9398000af0, table_list=0x7f9398011f70, fields=..., values_list=..., update_fields=..., update_values=..., duplic=DUP_ERROR, ignore=false) at /data/src/10.4/sql/sql_insert.cc:1078
      #16 0x00005588cfacc847 in mysql_execute_command (thd=0x7f9398000af0) at /data/src/10.4/sql/sql_parse.cc:4528
      #17 0x00005588cfad8fd1 in mysql_parse (thd=0x7f9398000af0, rawbuf=0x7f9398011e68 "INSERT INTO t1 VALUES (1), (2), (3), (4), (5)", length=45, parser_state=0x7f9400208160, is_com_multi=false, is_next_command=false) at /data/src/10.4/sql/sql_parse.cc:7900
      #18 0x00005588cfad85cd in wsrep_mysql_parse (thd=0x7f9398000af0, rawbuf=0x7f9398011e68 "INSERT INTO t1 VALUES (1), (2), (3), (4), (5)", length=45, parser_state=0x7f9400208160, is_com_multi=false, is_next_command=false) at /data/src/10.4/sql/sql_parse.cc:7704
      #19 0x00005588cfac4060 in dispatch_command (command=COM_QUERY, thd=0x7f9398000af0, packet=0x7f93980083a1 "INSERT INTO t1 VALUES (1), (2), (3), (4), (5)", packet_length=45, is_com_multi=false, is_next_command=false) at /data/src/10.4/sql/sql_parse.cc:1827
      #20 0x00005588cfac282d in do_command (thd=0x7f9398000af0) at /data/src/10.4/sql/sql_parse.cc:1360
      #21 0x00005588cfc4be43 in do_handle_one_connection (connect=0x5588d4086460) at /data/src/10.4/sql/sql_connect.cc:1412
      #22 0x00005588cfc4bb92 in handle_one_connection (arg=0x5588d4086460) at /data/src/10.4/sql/sql_connect.cc:1316
      #23 0x00005588d0655e47 in pfs_spawn_thread (arg=0x5588d3b27840) at /data/src/10.4/storage/perfschema/pfs.cc:1869
      #24 0x00007f94110b54a4 in start_thread (arg=0x7f9400209700) at pthread_create.c:456
      #25 0x00007f940f1e9d0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
      

      Reproducible on 10.4, 10.5.
      Not reproducible on 10.3.

      Attachments

        Issue Links

          Activity

            jplindst,

            The issue is closed as fixed, but it doesn't have any linked commits, and neither does the one marked as duplicate. Could you please clarify?

            elenst Elena Stepanova added a comment - jplindst , The issue is closed as fixed, but it doesn't have any linked commits, and neither does the one marked as duplicate. Could you please clarify?

            People

              jplindst Jan Lindström (Inactive)
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.