[MDEV-24326] MariaDB crash loop on DELETE Created: 2020-12-01  Updated: 2021-04-19  Resolved: 2021-01-06

Status: Closed
Project: MariaDB Server
Component/s: Replication, Storage Engine - InnoDB
Affects Version/s: 10.5.8
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Todd Coker (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 2
Labels: foreign-keys, need_feedback
Environment:

CentOS 7


Issue Links:
Duplicate
duplicates MDEV-23033 All slaves crash once in ~24 hours an... Closed
Relates

 Description   

201201  8:33:05 [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.5.8-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=4
max_threads=502
thread_count=12
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1236136 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7fed400009b8
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 = 0x7fed8c21cc40 thread_stack 0x49000
Can't start addr2line
/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x560a4856437e]
/usr/sbin/mariadbd(handle_fatal_signal+0x307)[0x560a47f72fe7]
/lib64/libpthread.so.0(+0xf630)[0x7ff3d27fa630]
/usr/sbin/mariadbd(+0xc5a6d4)[0x560a4825d6d4]
/usr/sbin/mariadbd(+0xd5599a)[0x560a4835899a]
/usr/sbin/mariadbd(+0xd5707d)[0x560a4835a07d]
/usr/sbin/mariadbd(+0xd58e12)[0x560a4835be12]
/usr/sbin/mariadbd(+0xd2a631)[0x560a4832d631]
/usr/sbin/mariadbd(+0xd1485d)[0x560a4831785d]
/usr/sbin/mariadbd(+0xd53818)[0x560a48356818]
/usr/sbin/mariadbd(+0xd576fb)[0x560a4835a6fb]
/usr/sbin/mariadbd(+0xd58e12)[0x560a4835be12]
/usr/sbin/mariadbd(+0xd2d0fb)[0x560a483300fb]
/usr/sbin/mariadbd(+0xc56ea1)[0x560a48259ea1]
/usr/sbin/mariadbd(_ZN7handler13ha_delete_rowEPKh+0x21e)[0x560a47f8043e]
/usr/sbin/mariadbd(_ZN21Delete_rows_log_event11do_exec_rowEP14rpl_group_info+0x13f)[0x560a4808be6f]
/usr/sbin/mariadbd(_ZN14Rows_log_event14do_apply_eventEP14rpl_group_info+0x31c)[0x560a48080f1c]
/usr/sbin/mariadbd(+0x6b8c1f)[0x560a47cbbc1f]
/usr/sbin/mariadbd(+0x8ac71e)[0x560a47eaf71e]
/usr/sbin/mariadbd(handle_rpl_parallel_thread+0x7db)[0x560a47eb1d5b]
/usr/sbin/mariadbd(+0xbbb79d)[0x560a481be79d]
/lib64/libpthread.so.0(+0x7ea5)[0x7ff3d27f2ea5]
/lib64/libc.so.6(clone+0x6d)[0x7ff3d091b96d]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fed54819dcb): DELETE FROM `ECORE`.`ORGANIZATION` WHERE `ORG_SID` = '527237'
 
Connection ID (thread ID): 10
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,not_null_range_scan=off
 
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.
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             127949               127949               processes 
Max open files            16384                16384                files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       127949               127949               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



 Comments   
Comment by Andrei Elkin [ 2021-01-06 ]

The reported stack and presence of FK constraint suggests it's a duplicate of a fixed one.

Comment by Andrei Elkin [ 2021-01-06 ]

See MDEV-23033 for the fix versions.

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