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

innodb.log_file_name fails on Assertion `!after_apply || !(blocks).end' in recv_sys_t::clear

    XMLWordPrintable

Details

    Description

      The failure happens fairly well after a sequence of tests, e.g.

      perl ./mtr --mem --noreorder innodb.innodb_bug53046 innodb.innodb_bug56143 innodb.innodb_bug59307 innodb.innodb_bug59733 innodb.innodb_bug84958 innodb.innodb_stats_rename_table innodb.innodb_sys_var_valgrind innodb.insert-before-delete innodb.instant_alter_bugs innodb.lock_delete_updated innodb.log_file_name
      

      The sequence can be reduced further, but the probability of the failure seems to be decreasing. The shortest I could get it with was

      innodb.innodb_bug53046 innodb.innodb_bug56143 innodb.innodb_bug59733 innodb.innodb_bug84958 innodb.innodb_sys_var_valgrind innodb.insert-before-delete innodb.instant_alter_bugs innodb.log_file_name
      

      10.5 ea0b1ccd

      mariadbd: /data/src/10.5/storage/innobase/log/log0recv.cc:969: void recv_sys_t::clear(): Assertion `!after_apply || !(blocks).end' failed.
      231109  1:59:59 [ERROR] mysqld got signal 6 ;
       
      #9  0x00007eff45053e32 in __GI___assert_fail (assertion=0x5635e41bdb60 "!after_apply || !(blocks).end", file=0x5635e41bc100 "/data/src/10.5/storage/innobase/log/log0recv.cc", line=969, function=0x5635e41bdb20 "void recv_sys_t::clear()") at ./assert/assert.c:101
      #10 0x00005635e2b61c5a in recv_sys_t::clear (this=0x5635e546d920 <recv_sys>) at /data/src/10.5/storage/innobase/log/log0recv.cc:969
      #11 0x00005635e2b3af56 in recv_sys_t::close (this=0x5635e546d920 <recv_sys>) at /data/src/10.5/storage/innobase/log/log0recv.cc:913
      #12 0x00005635e2b32f90 in log_t::close (this=0x5635e62e55c0 <log_sys>) at /data/src/10.5/storage/innobase/log/log0log.cc:1350
      #13 0x00005635e2df6ae0 in innodb_shutdown () at /data/src/10.5/storage/innobase/srv/srv0start.cc:2083
      #14 0x00005635e2942f37 in innodb_init (p=0x615000002d98) at /data/src/10.5/storage/innobase/handler/ha_innodb.cc:4063
      #15 0x00005635e1ee5c2c in ha_initialize_handlerton (plugin=0x62100002e010) at /data/src/10.5/sql/handler.cc:651
      #16 0x00005635e1710726 in plugin_do_initialize (plugin=0x62100002e010, state=@0x7ffe981afdd0: 4) at /data/src/10.5/sql/sql_plugin.cc:1450
      #17 0x00005635e1711069 in plugin_initialize (tmp_root=0x7ffe981b0530, plugin=0x62100002e010, argc=0x5635e59dae00 <remaining_argc>, argv=0x61b000001cf8, options_only=false) at /data/src/10.5/sql/sql_plugin.cc:1503
      #18 0x00005635e1712b0a in plugin_init (argc=0x5635e59dae00 <remaining_argc>, argv=0x61b000001cf8, flags=0) at /data/src/10.5/sql/sql_plugin.cc:1761
      #19 0x00005635e13cbad5 in init_server_components () at /data/src/10.5/sql/mysqld.cc:4939
      #20 0x00005635e13cdc0b in mysqld_main (argc=164, argv=0x61b000001cf8) at /data/src/10.5/sql/mysqld.cc:5533
      #21 0x00005635e13b7979 in main (argc=23, argv=0x7ffe981b2298) at /data/src/10.5/sql/main.cc:25
      

      Attachments

        Activity

          People

            marko Marko Mäkelä
            elenst Elena Stepanova
            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.