Description:
mysqld was restarted in a few week period.
and then also, today mysqld was restarted
mysqld error log is next.
---
2016-10-11 08:42:14 7fe9326b7700 InnoDB: Assertion failure in thread 140639550011136 in file row0ins.cc line 277
InnoDB: Failing assertion: *cursor->index->name == TEMP_INDEX_PREFIX
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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.
23:42:14 UTC - 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.
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.
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=41
max_threads=300
thread_count=19
connection_count=17
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787711 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fe8dc000990
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 = 7fe9326b67e0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8e1f85]
/usr/sbin/mysqld(handle_fatal_signal+0x494)[0x666ca4]
/lib64/libpthread.so.0[0x367080f710]
/lib64/libc.so.6(gsignal+0x35)[0x3670032625]
/lib64/libc.so.6(abort+0x175)[0x3670033e05]
/usr/sbin/mysqld[0x988286]
/usr/sbin/mysqld[0x98ad23]
/usr/sbin/mysqld[0x98c60f]
/usr/sbin/mysqld[0x998d44]
/usr/sbin/mysqld[0x910601]
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0xff)[0x5ae2ff]
/usr/sbin/mysqld(_ZN12ha_partition9write_rowEPh+0x140)[0xb269b0]
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0xab)[0x5ae2ab]
/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP9COPY_INFOS4_+0x1fc)[0x6c879c]
/usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xb70)[0x6cfd80]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x361d)[0x6e6c0d]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x380)[0x6e8420]
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x7bd)[0x8817cd]
/usr/sbin/mysqld(_ZN9Log_event11apply_eventEP14Relay_log_info+0x74)[0x884444]
/usr/sbin/mysqld(_Z26apply_event_and_update_posPP9Log_eventP3THDP14Relay_log_info+0x263)[0x8b29c3]
/usr/sbin/mysqld[0x8b54a2]
/usr/sbin/mysqld(handle_slave_sql+0xb19)[0x8b6f89]
/usr/sbin/mysqld(pfs_spawn_thread+0x12d)[0xb0efdd]
/lib64/libpthread.so.0[0x36708079d1]
/lib64/libc.so.6(clone+0x6d)[0x36700e88fd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fe8dc3da4d4): INSERT INTO `DATA1`...
Connection ID (thread ID): 121
Status: NOT_KILLED
---
i check index status.
mysqlcheck -c -v -uroot -p db1 DATA1
Enter password:
# Connecting to localhost...
mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'CHECK TABLE ... '
DATA1 table index was corrupt.
this system is consist of mysql master 1(physical server), slave 4(vm server).
phyiscal master is normal. but all 4 slave , mysqld was occured crash in turn after a few days.
DATA1 table use compression and partition.
How to repeat:
intentionally this problem was not repeated.
but, in nessary, it is happening in what day intervals, peridically at my production system.
