[MDEV-17130] Sudden crash of MariaDB Galera cluster 2 nodes + arbitrator Created: 2018-09-04  Updated: 2022-01-21  Resolved: 2022-01-21

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.2.14
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Davide Pennica Assignee: Jan Lindström (Inactive)
Resolution: Incomplete Votes: 0
Labels: crash, galera
Environment:

Cluster Galera with two nodes and one arbitrator

Ubuntu 16.04
Linux 4.4.0-116-generic #140-Ubuntu SMP
Intel(R) Xeon(R) CPU X7560 @ 2.27GHz
RAM 8GB

Attachments: HTML File log_crash    

 Description   

During alter table to add two columns on a table with 140000 records we suffer a complete crash of all nodes of the cluster.

The only way to open the system again was to create a new cluster.

In the attachment the log extract.

 Comments   
Comment by Mikhail Zheltukhin [ 2018-09-13 ]

Same issue, no galera clustering :

We think the query pointer is invalid, but we will try to print it anyway.
Query: ALTER TABLE `table` ADD CONSTRAINT `constraint` FOREIGN KEY (`fk`) REFERENCES `ggg` (`id`)

(Looks like pointer is valid, cause after crash could not create or delete constraint with that name)

=====
2018-09-12 17:30:01 140022103770880 [ERROR] Invalid (old?) table or database name '#sql-46df_1f2100c9'
2018-09-12 17:30:01 140017644730112 [ERROR] Invalid (old?) table or database name '#sql-46df_1f2100c9'
2018-09-12 17:30:22 0x7f596f5bc700 InnoDB: Assertion failure in file /mariadb-10.2.14/work/mysql/storage/innobase/handler/ha_innodb.cc line 6032
InnoDB: Failing assertion: share->idx_trans_tbl.index_count == mysql_num_index
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/
InnoDB: about forcing recovery.
180912 17:30:22 [ERROR] 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.

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.2.14-MariaDB-log
key_buffer_size=134217728
read_buffer_size=524288
max_used_connections=621
max_threads=502
thread_count=313
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2475750 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f5914020be8
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 = 0x7f596f5bbe88 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x5590641134a9]
/usr/sbin/mysqld(handle_fatal_signal+0x57b)[0x559063c6063b]
/lib64/libpthread.so.0(+0x13ef0)[0x7f5cb693bef0]
/lib64/libc.so.6(gsignal+0x110)[0x7f5cb5459f80]
/lib64/libc.so.6(abort+0x17a)[0x7f5cb545bc4a]
/usr/sbin/mysqld(+0x3ff6d4)[0x559063a5e6d4]
/usr/sbin/mysqld(+0x77ad40)[0x559063dd9d40]
/usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcij+0x2a)[0x559063c6432a]
/usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x7de)[0x559063b9b29e]
/usr/sbin/mysqld(_ZN3THD20open_temporary_tableEP15TMP_TABLE_SHAREPKcb+0x5d)[0x559063c11f9d]
/usr/sbin/mysqld(_ZN3THD25create_and_open_tmp_tableEP10handlertonP34st_mysql_const_unsigned_lex_stringPKcS5_S5_b+0x32)[0x559063c13bd2]
/usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P14HA_CREATE_INFOP10TABLE_LISTP10Alter_infojP8st_orderb+0x3c1c)[0x559063b7c62c]
/usr/sbin/mysqld(_ZN19Sql_cmd_alter_table7executeEP3THD+0x50c)[0x559063bc0e0c]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0xd93)[0x559063afdd93]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x289)[0x559063b04189]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xf73)[0x559063b057d3]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xdf)[0x559063b06d9f]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x204)[0x559063bbe264]
/usr/sbin/mysqld(handle_one_connection+0x34)[0x559063bbe334]
/lib64/libpthread.so.0(+0x7907)[0x7f5cb692f907]
/lib64/libc.so.6(clone+0x3f)[0x7f5cb551dccf]

Comment by Stan Iwanow [ 2018-12-18 ]

Also no clustering same issue:

2018-12-18 09:39:35 7f6c653c1700  InnoDB: Assertion failure in thread 140103531632384 in file ha_innodb.cc line 6092
 
InnoDB: Failing assertion: share->idx_trans_tbl.index_count == mysql_num_index
 
InnoDB: We intentionally generate a memory trap.
 
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
 
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.
 
181218  9:39:35 [ERROR] 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.
 
 
 
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.1.37-MariaDB-0+deb9u1
 
key_buffer_size=16777216
 
read_buffer_size=131072
 
max_used_connections=17
 
max_threads=153
 
thread_count=13
 
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 352467 K  bytes of memory
 
Hope that's ok; if not, decrease some variables in the equation.
 
 
 
Thread pointer: 0x7f6b2273c008
 
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 = 0x7f6c653c0cb8 thread_stack 0x30000
 
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55a3c08c739e]
 
/usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x55a3c040897d]
 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f6c68bfb0c0]
 
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f6c67768fff]
 
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f6c6776a42a]
 
/usr/sbin/mysqld(+0x828005)[0x55a3c068c005]
 
/usr/sbin/mysqld(+0x835559)[0x55a3c0699559]
 
/usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcij+0x33)[0x55a3c040ccd3]
 
/usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0xb63)[0x55a3c0321dc3]
 
/usr/sbin/mysqld(_Z19open_table_uncachedP3THDP10handlertonP34st_mysql_const_unsigned_lex_stringPKcS6_S6_bb+0x1c6)[0x55a3c022c126]
 
/usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P14HA_CREATE_INFOP10TABLE_LISTP10Alter_infojP8st_orderb+0x3d5e)[0x55a3c030743e]
 
/usr/sbin/mysqld(_ZN19Sql_cmd_alter_table7executeEP3THD+0x5c9)[0x55a3c034e499]
 
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x152c)[0x55a3c0270a7c]
 
/usr/sbin/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x4de)[0x55a3c028d59e]
 
/usr/sbin/mysqld(+0x42971f)[0x55a3c028d71f]
 
/usr/sbin/mysqld(_Z22mysql_sql_stmt_executeP3THD+0x12b)[0x55a3c028de5b]
 
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x243f)[0x55a3c027198f]
 
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x311)[0x55a3c0278801]
 
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x2615)[0x55a3c027c165]
 
/usr/sbin/mysqld(_Z10do_commandP3THD+0x179)[0x55a3c027c9a9]
 
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1d2)[0x55a3c034b842]
 
/usr/sbin/mysqld(handle_one_connection+0x40)[0x55a3c034b9a0]
 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7f6c68bf1494]
 
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f6c6781eacf]
 
 
 
Trying to get some variables.
 
Some pointers may be invalid and cause the dump to abort.
 
Query (0x7f6b21344520): ALTER TABLE article_flag ADD CONSTRAINT FK_article_flag_article_id_id FOREIGN KEY (article_id) REFERENCES article (id)
 
Connection ID (thread ID): 1959
 
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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=off
 
 
 
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.
 
2018-12-18  9:39:43 140064358576576 [Note] Using unique option prefix 'innodb_open_file' is error-prone and can break in the future. Please use the full name 'innodb-open-files' instead.
 
2018-12-18  9:39:43 140064358576576 [Note] InnoDB: Using mutexes to ref count buffer pool pages

System:
Intel Xeon Processor (Skylake, IBRS)
RAM 8G, Debian Stretch
4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64

Comment by Jan Lindström (Inactive) [ 2022-01-21 ]

Can you please try again with more recent version of MariaDB and Galera library.

Generated at Thu Feb 08 08:34:08 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.