[MDEV-17997] mariadb crash down Created: 2018-12-13  Updated: 2018-12-22  Resolved: 2018-12-22

Status: Closed
Project: MariaDB Server
Component/s: Optimizer - CTE
Affects Version/s: 10.2.14
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: yongjian.wu Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: galera
Environment:

3.10.0-514.26.2.el7.x86_64


Attachments: Text File show engine innodb status.txt     Text File show engine performance_schema status.txt     Text File show global status.txt     Text File show global variables.txt     Text File sql.txt    
Issue Links:
Duplicate
duplicates MDEV-16353 Server crash on query with CTE Closed

 Description   

when we execute the sql, then the db crash down immedaite with below error,have attach the db status and the sql statement on the attachement,if need any more information please comment,thank you.

181213 18:14:18 [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.2.14-MariaDB-log 
key_buffer_size=134217728 
read_buffer_size=131072 
max_used_connections=119 
max_threads=30001 
thread_count=65 
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 987684536 K bytes of memory 
Hope that's ok; if not, decrease some variables in the equation. 
 
Thread pointer: 0x7f442400fcd8 
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 = 0x7f458033ec58 thread_stack 0x30000 
/opt/maria10.1/bin/mysqld(my_print_stacktrace+0x29)[0x7f4999efa8c9] 
/opt/maria10.1/bin/mysqld(handle_fatal_signal+0x33d)[0x7f4999a1d5ed] 
sigaction.c:0(__restore_rt)[0x7f4998fa2370] 
sql/sql_union.cc:603(st_select_lex_unit::prepare(THD*, select_result*, unsigned long))[0x7f499992ef43] 
sql/sql_cte.cc:964(With_element::prepare_unreferenced(THD*))[0x7f49999b3edc] 
sql/sql_cte.cc:713(With_clause::prepare_unreferenced_elements(THD*))[0x7f49999b3f63] 
sql/sql_select.cc:891(JOIN::prepare(TABLE_LIST*, unsigned int, Item*, unsigned int, st_order*, bool, st_order*, Item*, st_order*, st_select_lex*, st_select_lex_unit*))[0x7f49998e3eca] 
sql/sql_select.cc:3739(mysql_select(THD*, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*))[0x7f49998f2180] 
sql/sql_select.cc:376(handle_select(THD*, LEX*, select_result*, unsigned long))[0x7f49998f24bb] 
sql/sql_parse.cc:6469(execute_sqlcom_select(THD*, TABLE_LIST*))[0x7f49997eaa30] 
sql/sql_parse.cc:3479(mysql_execute_command(THD*))[0x7f49998a3084] 
sql/sql_parse.cc:7915(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x7f49998a8fc0] 
sql/sql_parse.cc:7729(wsrep_mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x7f49998a9819] 
sql/sql_parse.cc:1797(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x7f49998aae58] 
sql/sql_parse.cc:1371(do_command(THD*))[0x7f49998aca78] 
sql/threadpool_common.cc:366(tp_callback(TP_connection*))[0x7f499999d65f] 
sql/threadpool_generic.cc:1604(worker_main(void*))[0x7f49999f93ee] 
perfschema/pfs.cc:1865(pfs_spawn_thread)[0x7f4999ec3d74] 
pthread_create.c:0(start_thread)[0x7f4998f9adc5] 
/lib64/libc.so.6(clone+0x6d)[0x7f499715676d] 
 
Trying to get some variables. 
Some pointers may be invalid and cause the dump to abort. 
Query (0x7f4424096990): with tmp1 as( SELECT DISTINCT(Qty_Asset) CurrencyCode FROM board ), tmp2 as( select '' TransferType, 'Previous Day Ending Balance' TransferTypeName, 1 sort union all select 'BUY', 'Client Buy', 2 union all select 'SELL', 'Client Sell', 3 union all select 'DEPOSIT', 'Transfer (Deposit)', 4 union all select 'WITHDRAWAL', 'Transfers (Withdraw)', 5 ), tmp3 as( SELECT Asset_Name , SUM(ifnull(Buy_Amount_T,0)) ClientBuy , SUM(ifnull(Sell_Amount_T,0)) ClientSell , SUM(ifnull(Deposit_Qty_T,0)) TransferDeposit , SUM(ifnull(Withdrawal_Qty_T,0)) TransfersWithdraw , SUM(ifnull(Safekeep_Other_Balance,0)) PreviousDayEndingBalance FROM asset_hist INNER JOIN tmp1 ON Asset_Name = tmp1.CurrencyCode WHERE Broker_ID = 'VC' AND Trade_D = '20180530' GROUP BY Asset_Name ), tmp4 as( SELECT Client_ID,CASE WHEN Transfer_Type = 'TRADE' THEN Ord_Side ELSE Transfer_Type END TransferType,Ord_Side,SUM(Trade_Qty) FROM report_customer_ledger INNER JOIN tmp1 ON Asset_Pair = tmp1.CurrencyCode WHERE Broker_ID = 'VC' AND Settlement_D = '2018-05-30' GROUP BY Client_ID,Transfer_Type,Ord_Side ) select * from tmp4 
Connection ID (thread ID): 224 
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=on,condition_pushdown_for_derived=on 
 
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-13 18:19:46 139658452334784 [Note] CONNECT: Version 1.



 Comments   
Comment by Alice Sherepa [ 2018-12-13 ]

The crash looks similar to MDEV-16353, which was fixed in 10.2.16.
Is it suitable for you to try MariaDB >=10.2.16?

Comment by yongjian.wu [ 2018-12-14 ]

okay,i will have a try on it. Thank you

Comment by yongjian.wu [ 2018-12-19 ]

Hi Alice,have test it on the Maria that Version >=10.2.16 is seems no problem ,thanks for you help

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