Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.3.18
Description
All 3 nodes in Galera cluster crash as follows:
200219 12:29:11 [ERROR] 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.
|
|
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.3.18-*-MariaDB-*-log
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=82
|
max_threads=852
|
thread_count=90
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2004324 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x7f18cc0009a8
|
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 = 0x7f1a4c8ecd00 thread_stack 0x49000
|
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5563d5d0e7be]
|
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x5563d579aa1f]
|
sigaction.c:0(__restore_rt)[0x7f1c83e6d630]
|
:0(__memcmp_sse4_1)[0x7f1c81c9ec60]
|
src/key_set.hpp:618(galera::KeySetOut::KeyPart::match(void const*, unsigned long) const)[0x7f1c46147f36]
|
src/write_set_ng.hpp:524(galera::WriteSetOut::append_key(galera::KeyData const&))[0x7f1c461a0578]
|
/usr/sbin/mysqld(+0x93aa73)[0x5563d592da73]
|
/usr/sbin/mysqld(+0x94c45b)[0x5563d593f45b]
|
/usr/sbin/mysqld(+0x94cc07)[0x5563d593fc07]
|
/usr/sbin/mysqld(_ZN7handler16update_first_rowEPh+0x112)[0x5563d57a00e2]
|
/usr/sbin/mysqld(+0xcf2743)[0x5563d5ce5743]
|
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0xc6)[0x5563d57a6496]
|
/usr/sbin/mysqld(_ZN19sequence_definition5writeEP5TABLEb+0xb5)[0x5563d56ff335]
|
/usr/sbin/mysqld(_ZN8SEQUENCE10next_valueEP5TABLEbPi+0x11b)[0x5563d56ff9fb]
|
/usr/sbin/mysqld(_ZN17Item_func_nextval7val_intEv+0x12d)[0x5563d5809c9d]
|
/usr/sbin/mysqld(_ZN14Item_func_plus6int_opEv+0x1d)[0x5563d580b11d]
|
/usr/sbin/mysqld(_ZNK12Type_handler18Item_send_longlongEP4ItemP8ProtocolP8st_value+0x19)[0x5563d56f0b79]
|
/usr/sbin/mysqld(_ZN8Protocol19send_result_set_rowEP4ListI4ItemE+0x103)[0x5563d54feef3]
|
/usr/sbin/mysqld(_ZN11select_send9send_dataER4ListI4ItemE+0x53)[0x5563d556d243]
|
/usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0xbab)[0x5563d560e77b]
|
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x33)[0x5563d560e9b3]
|
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x11a)[0x5563d560cd8a]
|
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1bc)[0x5563d560d88c]
|
/usr/sbin/mysqld(+0x4c762e)[0x5563d54ba62e]
|
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x28ce)[0x5563d55b0b3e]
|
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x36c)[0x5563d55b6e9c]
|
/usr/sbin/mysqld(+0x5c47c9)[0x5563d55b77c9]
|
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x16e5)[0x5563d55b9725]
|
/usr/sbin/mysqld(_Z10do_commandP3THD+0x13e)[0x5563d55bb4be]
|
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x221)[0x5563d5696cc1]
|
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x5563d5696d8d]
|
/usr/sbin/mysqld(+0xccef2d)[0x5563d5cc1f2d]
|
pthread_create.c:0(start_thread)[0x7f1c83e65ea5]
|
/lib64/libc.so.6(clone+0x6d)[0x7f1c81c328cd]
|
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x7f18cc00fcf0): SELECT (seq.NEXTVAL+0) FROM dual
|
Connection ID (thread ID): 1913
|
Status: NOT_KILLED
|
I can not find any older MDEV for exactly this case.
Do we have any progress on this? Any idea about the root cause?