MySQL Cluster SQL Node Crashes at Startup if expire_logs_days is Set And There Are Old Binary Logs To Delete (Doc ID 1362684.1)

Last updated on MARCH 22, 2016

Applies to:

MySQL Cluster - Version 6.3 to 7.1 [Release 6.3 to 7.1]
Information in this document applies to any platform.

Symptoms

Under certain conditions, the SQL Node of a MySQL Cluster (v. 6.3, 7.0 or 7.1) can crash at startup with the following stack trace:

110916 13:58:00 - mysqld got signal 11 ;
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=8384512
read_buffer_size=131072
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338308 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
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 = (nil) thread_stack 0x40000
/usr/local/mysql/sbin/mysqld(my_print_stacktrace+0x33)[0x927513]
/usr/local/mysql/sbin/mysqld(handle_segfault+0x320)[0x61f2e0]
/lib64/libpthread.so.0[0x2b1715b9ae00]
/usr/local/mysql/sbin/mysqld(_Z26ha_binlog_index_purge_fileP3THDPKc+0x1e)[0x6f7e7e]
/usr/local/mysql/sbin/mysqld(_ZN13MYSQL_BIN_LOG17purge_index_entryEP3THDPyb+0x27d)[0x6b438d]
/usr/local/mysql/sbin/mysqld(_ZN13MYSQL_BIN_LOG10purge_logsEPKcbbbPy+0x144)[0x6b4724]
/usr/local/mysql/sbin/mysqld(_ZN13MYSQL_BIN_LOG22purge_logs_before_dateEl+0x174)[0x6b4994]
/usr/local/mysql/sbin/mysqld[0x61dd65]
/usr/local/mysql/sbin/mysqld(main+0x6b5)[0x620ae5]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x2b1716275304]
/usr/local/mysql/sbin/mysqld[0x569bb9]
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.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms