Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4.18
-
None
-
Debian 10 with official repositories on a KVM VM
Description
We are using a three node Galera cluster with MariaDB 10.4.18 from official repositories.
The three nodes are using the same configuration.
Since some weeks, we are facing some crashes after a node revival.
It's not reproducable every time unfortunately.
I don't know the exact version introducing this problem, it happened probably after our migration to 10.4.x)
I uploaded a crash we had yesterday. The backtrace seems to indicate it's related to table locking.
How it happened :
- In the morning we stopped galera01 for some maintenance operations on the underlying host.
- The cluster was working fine the whole day with only two nodes (galera02 et galera03).
- When we started again galera01 at 22:50:02, the donor node (galera02) crashed after some seconds.
- Then, all the three nodes started to crash in a loop until stabilize them after some minutes.
Some other times, the whole cluster totally crashed and we need to restart it manually.
The backtrace of the crash is similar to the other cases.
I can add some more debug messages if needed.
The full backtrace :
210310 22:50:03 [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.4.18-MariaDB-1:10.4.18+maria~buster |
key_buffer_size=16777216 |
read_buffer_size=131072 |
max_used_connections=5 |
max_threads=153 |
thread_count=15 |
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 353072 K bytes of memory |
Hope that's ok; if not, decrease some variables in the equation. |
|
|
Thread pointer: 0x7f9660001268 |
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 = 0x7f9824123e08 thread_stack 0x40000 |
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55d33bb277fe] |
/usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x55d33b61ab0d] |
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f9850da8730] |
/usr/sbin/mysqld(+0x64819d)[0x55d33b3aa19d] |
/usr/sbin/mysqld(_Z11lock_tablesP3THDP10TABLE_LISTjj+0x4a8)[0x55d33b3aff78] |
/usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDRK14DDL_options_stP10TABLE_LISTbjP19Prelocking_strategy+0x8a)[0x55d33b3b16ba] |
/usr/sbin/mysqld(_Z24open_n_lock_single_tableP3THDP10TABLE_LIST13thr_lock_typejP19Prelocking_strategy+0x41)[0x55d33b3b1761] |
/usr/sbin/mysqld(+0x8370c5)[0x55d33b5990c5] |
/usr/sbin/mysqld(_ZNK12Wsrep_schema12restore_viewEP3THDRKN5wsrep2idE+0xf8)[0x55d33b59bd88] |
/usr/sbin/mysqld(_ZN20Wsrep_server_service8log_viewEPN5wsrep21high_priority_serviceERKNS0_4viewE+0x4d4)[0x55d33b7970d4] |
/usr/sbin/mysqld(_ZN5wsrep12server_state7on_viewERKNS_4viewEPNS_21high_priority_serviceE+0x39b)[0x55d33bb9f95b] |
/usr/sbin/mysqld(+0xe4facc)[0x55d33bbb1acc] |
/usr/lib/galera/libgalera_smm.so(+0x5ccd9)[0x7f984d5accd9] |
/usr/lib/galera/libgalera_smm.so(+0x5cd18)[0x7f984d5acd18] |
/usr/lib/galera/libgalera_smm.so(+0x68398)[0x7f984d5b8398] |
/usr/lib/galera/libgalera_smm.so(+0x685ae)[0x7f984d5b85ae] |
/usr/lib/galera/libgalera_smm.so(+0x92dd8)[0x7f984d5e2dd8] |
/usr/lib/galera/libgalera_smm.so(+0x93061)[0x7f984d5e3061] |
/usr/lib/galera/libgalera_smm.so(+0x66cb0)[0x7f984d5b6cb0] |
/usr/lib/galera/libgalera_smm.so(+0x4248b)[0x7f984d59248b] |
/usr/sbin/mysqld(_ZN5wsrep18wsrep_provider_v2611run_applierEPNS_21high_priority_serviceE+0xe)[0x55d33bbaf4fe] |
/usr/sbin/mysqld(+0x836dff)[0x55d33b598dff] |
/usr/sbin/mysqld(_Z15start_wsrep_THDPv+0x388)[0x55d33b58aac8] |
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7f9850d9dfa3] |
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f98502b24cf] |
|
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x0): (null) |
Connection ID (thread ID): 17 |
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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on |
|
|
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ 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:
|
|
|
Writing a core file...
|
Working directory at /var/lib/mysql
|
Resource Limits:
|
Limit Soft Limit Hard Limit Units
|
Max cpu time unlimited unlimited seconds
|
Max file size unlimited unlimited bytes
|
Max data size unlimited unlimited bytes
|
Max stack size 8388608 unlimited bytes |
Max core file size 0 unlimited bytes |
Max resident set unlimited unlimited bytes
|
Max processes 38887 38887 processes |
Max open files 1048576 1048576 files |
Max locked memory 65536 65536 bytes |
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 38887 38887 signals |
Max msgqueue size 819200 819200 bytes |
Max nice priority 0 0 |
Max realtime priority 0 0 |
Max realtime timeout unlimited unlimited us
|
Core pattern: core
|
Attachments
Issue Links
- relates to
-
-
- Closed
-