Description:
I'm running a query to delete some record with a lot of cascades. After some time MySQL crashes and cannot recover.
2017-05-05 20:36:05 0x7f2da5ffb700 InnoDB: Assertion failure in thread 139834035255040 in file btr0cur.cc line 325
InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page)
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
20:36:05 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
2017-05-05T20:36:05.493521860Z
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=5
max_threads=151
thread_count=4
connection_count=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68190 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
2017-05-05T20:36:05.498553691Z
Thread pointer: 0x7f2da0000900
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 = 7f2da5ffae38 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2c)[0xe7fdcc]
mysqld(handle_fatal_signal+0x459)[0x7a9d39]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f2dc9157890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f2dc7b60067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f2dc7b61448]
mysqld[0x7804a7]
mysqld(_Z20btr_cur_latch_leavesP11buf_block_tRK9page_id_tRK11page_size_tmP9btr_cur_tP5mtr_t+0x8a8)[0x11218f8]
mysqld(_Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_t15page_cur_mode_tmP9btr_cur_tmPKcmP5mtr_t+0x1909)[0x112c749]
mysqld(_Z22row_search_index_entryP12dict_index_tPK8dtuple_tmP10btr_pcur_tP5mtr_t+0x106)[0x1079f56]
mysqld[0x1074f69]
mysqld(_Z14row_purge_stepP9que_thr_t+0x480)[0x1077820]
mysqld(_Z15que_run_threadsP9que_thr_t+0xa1c)[0x1024a2c]
mysqld(srv_worker_thread+0x4aa)[0x10aa87a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f2dc9150064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f2dc7c1362d]
2017-05-05T20:36:05.515637544Z
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED
2017-05-05T20:36:05.515648288Z
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.
How to repeat:
I'm using docker image and quite big DB with a lot of tables and records. Can I add any logs or crash dump that would help?
