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

InnoDB: Assertion failure in thread 139946191502080 in file row0ins.cc line 285

    Details

      Description

      After upgrading from 5.5 to 10.1.32 our imports of mysqldumps into warehouse database are failing...with the following in the error log.

      2018-07-12 10:39:38 7f47c3083b00  InnoDB: Assertion failure in thread 139946191502080 in file row0ins.cc line 285
      InnoDB: Failing assertion: *cursor->index->name == TEMP_INDEX_PREFIX
      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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      180712 10:39:38 [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.1.32-MariaDB
      key_buffer_size=17179869184
      read_buffer_size=131072
      max_used_connections=15
      max_threads=502
      thread_count=3
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17879995 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f473ed10008
      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 = 0x7f47c3083140 thread_stack 0x48400
      /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f5937629e2b]
      /usr/sbin/mysqld(handle_fatal_signal+0x4d5)[0x7f5937186a45]
      /lib64/libpthread.so.0(+0x3ccd20f7e0)[0x7f59367807e0]
      /lib64/libc.so.6(gsignal+0x35)[0x7f5934ba6495]
      /lib64/libc.so.6(abort+0x175)[0x7f5934ba7c75]
      /usr/sbin/mysqld(+0x89c3ad)[0x7f593744d3ad]
      /usr/sbin/mysqld(+0x89e5c4)[0x7f593744f5c4]
      /usr/sbin/mysqld(+0x89e9af)[0x7f593744f9af]
      /usr/sbin/mysqld(+0x8ab4da)[0x7f593745c4da]
      /usr/sbin/mysqld(+0x80182b)[0x7f59373b282b]
      /usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0x177)[0x7f59371905e7]
      /usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x71)[0x7f5936ff3ff1]
      /usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1291)[0x7f5936ffa8b1]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x40b6)[0x7f5937010ec6]
      row/row0ins.cc:285(row_ins_sec_index_entry_by_modify)[0x7f5937015d15]
      row/row0ins.cc:3067(row_ins_sec_index_entry(dict_index_t*, dtuple_t*, que_thr_t*))[0x7f59370187fe]
      row/row0mysql.cc:1445(row_insert_for_mysql(unsigned char*, row_prebuilt_t*))[0x7f5937018d9b]
      handler/ha_innodb.cc:8885(ha_innobase::write_row(unsigned char*))[0x7f59370d988f]
      sql/handler.cc:5950(handler::ha_write_row(unsigned char*))[0x7f59370d99c7]
      /lib64/libpthread.so.0(+0x3ccd207aa1)[0x7f5936778aa1]
      /lib64/libc.so.6(clone+0x6d)[0x7f5934c5cbcd]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f47df11f020): is an invalid pointer
      Connection ID (thread ID): 2821
      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=off
       
      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.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query: INSERT INTO `notes` VALUES
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                joe.oreste@xpressbet.com Joseph Oreste
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: