[MDEV-23012] Galera Nodes Crashes on updates for full table Created: 2020-06-25  Updated: 2020-11-09  Resolved: 2020-11-09

Status: Closed
Project: MariaDB Server
Component/s: Data Manipulation - Update, Galera
Affects Version/s: 10.4.13
Fix Version/s: N/A

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

Linux Debian 10, 7 Node-Cluster



 Description   

If update like 'UPDATE TABLE SET FIELD=0' executed on differrent nodes at the same time nodes crashes.

mysqld: /home/buildbot/buildbot/build/mariadb-10.4.13/wsrep-lib/src/client_state.cpp:237: int wsrep::client_state::after_statement(): Assertion `transaction_.state() == wsrep::transaction::s_aborted' failed.
200624 13:12:03 [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.4.13-MariaDB-1:10.4.13+maria~buster-log
key_buffer_size=536870912
read_buffer_size=131072
max_used_connections=60
max_threads=1002
thread_count=99
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2729375 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7fb3b4000c08
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 = 0x7fb583e23da8 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55daa7ce88de]
/usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x55daa77e0c4d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7fb8953a7730]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7fb8947ef7bb]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7fb8947da535]
/lib/x86_64-linux-gnu/libc.so.6(+0x2240f)[0x7fb8947da40f]
/lib/x86_64-linux-gnu/libc.so.6(+0x30102)[0x7fb8947e8102]
/usr/sbin/mysqld(_ZN5wsrep12client_state15after_statementEv+0x301)[0x55daa7d4d231]
/usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0xf21)[0x55daa7549421]
/usr/sbin/mysqld(_ZN7sp_head15execute_triggerEP3THDPK25st_mysql_const_lex_stringS4_P13st_grant_info+0x1b8)[0x55daa7549948]
/usr/sbin/mysqld(_ZN19Table_triggers_list16process_triggersEP3THD14trg_event_type20trg_action_time_typeb+0x11c)[0x55daa767a85c]
/usr/sbin/mysqld(_Z36fill_record_n_invoke_before_triggersP3THDP5TABLER4ListI4ItemES6_b14trg_event_type+0x76)[0x55daa7582e86]
/usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_orderybPySA_+0x17b3)[0x55daa76883a3]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x26ca)[0x55daa75db5fa]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1c9)[0x55daa75e1279]
/usr/sbin/mysqld(+0x6a7adc)[0x55daa75e1adc]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x205e)[0x55daa75e41ee]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x104)[0x55daa75e4ba4]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x25e)[0x55daa76c5cee]
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x55daa76c5dbd]
/usr/sbin/mysqld(+0xd5f38b)[0x55daa7c9938b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7fb89539cfa3]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fb8948b14cf]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fb3b400fff0): UPDATE mediaconv_provision SET changed=0
Connection ID (thread ID): 3126
Status: KILL_QUERY
 
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 http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /datab...
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             768134               768134               processes
Max open files            16364                16364                files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       768134               768134               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: co...



 Comments   
Comment by Jan Lindström (Inactive) [ 2020-10-07 ]

Hi, can you please provide show create table for problematic table, attach error logs from both nodes and if this is easily repeatable please provide detailed steps how to reproduce.

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