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

Node keep on IST every a few hours (InnoDB: Failing assertion: !cursor->index->is_committed())

    XMLWordPrintable

Details

    Description

      Please help me. What does this error mean?
      How to fix this?
      It keep on IST every few hours

      this is the log file

      2018-07-21 05:18:04 0x7f34bc1e6700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.13/storage/innobase/row/row0ins.cc line 269
      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/xtradbinnodb-recovery-modes/
      InnoDB: about forcing recovery.
      180721 5:18:04 [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.2.13-MariaDB-log
      key_buffer_size=131072
      read_buffer_size=262144
      max_used_connections=3
      max_threads=514
      thread_count=45
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67513673 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f340c000b58
      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 = 0x7f34bc1e5c9f thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x563b6d8e66ce]
      /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x563b6d36e085]
      /lib64/libpthread.so.0(+0xf5e0)[0x7f44037275e0]
      /lib64/libc.so.6(gsignal+0x37)[0x7f4401c341f7]
      :0(__GI_raise)[0x7f4401c358e8]
      /usr/sbin/mysqld(+0x4277c0)[0x563b6d1247c0]
      /usr/sbin/mysqld(+0x90359f)[0x563b6d60059f]
      ut/ut0rbt.cc:221(rbt_tree_add_child(ib_rbt_t const*, ib_rbt_bound_t*, ib_rbt_node_t*) [clone .isra.4] [clone .part.5])[0x563b6d6032a2]
      row/row0ins.cc:268(row_ins_sec_index_entry_low(unsigned long, unsigned long, dict_index_t*, mem_block_info_t*, mem_block_info_t*, dtuple_t*, unsigned long, que_thr_t*, bool))[0x563b6d605658]
      row/row0ins.cc:3248(row_ins_sec_index_entry(dict_index_t*, dtuple_t*, que_thr_t*, bool))[0x563b6d61512a]
      row/row0ins.cc:3293(row_ins_step(que_thr_t*))[0x563b6d55a283]
      row/row0mysql.cc:1411(row_insert_for_mysql(unsigned char const*, row_prebuilt_t*))[0x563b6d378cdf]
      handler/ha_innodb.cc:8455(ha_innobase::write_row(unsigned char*))[0x563b6d1c055f]
      sql/handler.cc:6001(handler::ha_write_row(unsigned char*))[0x563b6d1c0ecc]
      sql/sql_insert.cc:1929(write_record(THD*, TABLE*, st_copy_info*))[0x563b6d22048f]
      sql/sql_insert.cc:3757(select_insert::send_data(List<Item>&))[0x563b6d208cc3]
      sql/sql_select.cc:19859(end_send(JOIN*, st_join_table*, bool))[0x563b6d2108d4]
      sql/sql_class.h:3602(THD::get_stmt_da())[0x563b6d22fcdf]
      sql/sql_select.cc:18236(JOIN::exec_inner())[0x563b6d22fef3]
      sql/sql_select.cc:3362(JOIN::exec())[0x563b6d23004a]
      sql/sql_select.cc:3763(mysql_select(THD*, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*))[0x563b6d230ba4]
      sql/sql_select.cc:376(handle_select(THD*, LEX*, select_result*, unsigned long))[0x563b6d1e167a]
      sql/sql_parse.cc:4525(mysql_execute_command(THD*))[0x563b6d499246]
      sql/sp_head.cc:3247(sp_instr_stmt::exec_core(THD*, unsigned int*))[0x563b6d49f45d]
      sql/sp_head.cc:3009(sp_lex_keeper::reset_lex_and_exec_core(THD*, unsigned int*, bool, sp_instr*))[0x563b6d49fa35]
      sql/sp_head.cc:3163(sp_instr_stmt::execute(THD*, unsigned int*))[0x563b6d49c280]
      sql/sp_head.cc:1329(sp_head::execute(THD*, bool))[0x563b6d49da0f]
      sql/sp_head.cc:2117(sp_head::execute_procedure(THD*, List<Item>*))[0x563b6d295f91]
      sql/event_data_objects.cc:1433(Event_job_data::execute(THD*, bool))[0x563b6d4d5473]
      sql/event_scheduler.cc:315(Event_worker_thread::run(THD*, Event_queue_element_for_exec*))[0x563b6d4d553d]
      /lib64/libpthread.so.0(+0x7e25)[0x7f440371fe25]
      /lib64/libc.so.6(clone+0x6d)[0x7f4401cf734d]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f328c0167b0): INSERT INTO xx SELECT * FROM xx WHERE xx
      Connection ID (thread ID): 118
      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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on

      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              noorsyamiera92 Syamiera
              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.