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

InnoDB: Failing assertion: !cursor->index->is_committed() in row0ins.cc

    XMLWordPrintable

    Details

      Description

      Server got stuck in a crash loop with the below crash. There were some log messages suggesting table corruption that could possibly be related, though most are for a table not involved in the crash.

      2020-08-24 15:13:18 26 [ERROR] InnoDB: Record in index `tasks_ta_assignee_id_2c3ca866_fk_chronometer_userprofile_user_id` of table `db_name`.`table_name` was not found on update: TUPLE (info_bits=0, 2 fields): {[4]    (0x8004F4AF),[4] z| (0x807A7CF9)} at: COMPACT RECORD(info_bits=0, 2 fields): {[4]    (0x8004F4AF),[4] v  (0x8076E8A3)}
      

      2020-08-24 16:10:10 0x7f4ec43dc700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.4.14/storage/innobase/row/row0ins.cc line 218
      InnoDB: Failing assertion: !cursor->index->is_committed()
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      200824 16:10:10 [ERROR] mysqld got signal 6 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
       
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed, 
      something is definitely wrong and this may fail.
       
      Server version: 10.4.14-MariaDB-1:10.4.14+maria~bionic-log
      key_buffer_size=33554432
      read_buffer_size=16777216
      max_used_connections=121
      max_threads=2002
      thread_count=146
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 164086070 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f4dd8000c08
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x7f4ec43dbd98 thread_stack 0x30000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55938409855e]
      /usr/sbin/mysqld(handle_fatal_signal+0x515)[0x559383b13ea5]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x128a0)[0x7f658bb5d8a0]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f658a491f47]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f658a4938b1]
      /usr/sbin/mysqld(+0x587885)[0x55938381d885]
      /usr/sbin/mysqld(+0xada5b7)[0x559383d705b7]
      /usr/sbin/mysqld(+0xadf84c)[0x559383d7584c]
      /usr/sbin/mysqld(+0xb1ae67)[0x559383db0e67]
      /usr/sbin/mysqld(+0xb1b847)[0x559383db1847]
      /usr/sbin/mysqld(+0xaf2684)[0x559383d88684]
      /usr/sbin/mysqld(+0xa2ca68)[0x559383cc2a68]
      /usr/sbin/mysqld(_ZN7handler13ha_update_rowEPKhS1_+0x127)[0x559383b1f467]
      /usr/sbin/mysqld(_ZN21Update_rows_log_event11do_exec_rowEP14rpl_group_info+0x237)[0x559383c15d97]
      /usr/sbin/mysqld(_ZN14Rows_log_event14do_apply_eventEP14rpl_group_info+0x23c)[0x559383c08d3c]
      /usr/sbin/mysqld(+0x5c3d52)[0x559383859d52]
      /usr/sbin/mysqld(+0x7a2279)[0x559383a38279]
      /usr/sbin/mysqld(handle_rpl_parallel_thread+0xcf6)[0x559383a3da26]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7f658bb526db]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f658a574a3f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f4d9955485b): UPDATE `table_name` SET `archived` = 0, `title` = 'XXXXXXXXXXXXXXXXXX', `created_by_id` = 359245, `assignee_id` = 347523, `assignee_group_id` = NULL, `assigned_by_id` = 347523, `status_id` = 2, `category_id` = NULL, `priority` = 30, `due_date_id` = 1251132, `chain_link_id` = NULL, `created_at` = '2020-08-12 12:39:18', `updated_at` = '2020-08-24 12:08:42.970881' WHERE `tasks_task`.`id` = 7671933
      Connection ID (thread ID): 26
      Status: NOT_KILLED
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on
       
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /var/lib/mysql
      Resource Limits:
      Limit                     Soft Limit           Hard Limit           Units     
      Max cpu time              unlimited            unlimited            seconds   
      Max file size             unlimited            unlimited            bytes     
      Max data size             unlimited            unlimited            bytes     
      Max stack size            8388608              unlimited            bytes     
      Max core file size        0                    unlimited            bytes     
      Max resident set          unlimited            unlimited            bytes     
      Max processes             515014               515014               processes 
      Max open files            16384                16384                files     
      Max locked memory         16777216             16777216             bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       515014               515014               signals   
      Max msgqueue size         819200               819200               bytes     
      Max nice priority         0                    0                    
      Max realtime priority     0                    0                    
      Max realtime timeout      unlimited            unlimited            us        
      Core pattern: |/usr/share/apport/apport %p %s %c %d %P %E
      
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Coker Todd Coker
              Reporter:
              Coker Todd Coker
              Votes:
              0 Vote for this issue
              Watchers:
              8 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.