[MDEV-23057] wsrep::transaction::before_rollback(): Assertion `state() == s_executing || state() == s_preparing caused by mysqldump Created: 2020-06-30  Updated: 2020-12-30  Resolved: 2020-12-30

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

Type: Bug Priority: Major
Reporter: Richard Stracke Assignee: Jan Lindström (Inactive)
Resolution: Incomplete Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-22063 Assertion `0' failed in wsrep::transa... In Review
relates to MDEV-22222 Assertion `state() == s_executing || ... Closed
relates to MDEV-23025 int wsrep::transaction::before_rollba... Closed

 Description   

During mysqldump (without single-trasnaction)

galera crashed with

mysqld: /home/buildbot/buildbot/build/wsrep-lib/src/transaction.cpp:632: int wsrep::transaction::before_rollback(): Assertion `state() == s_executing || state() == s_preparing || state() == s_prepared || state() == s_must_abort || state() == s_aborting || state() == s_cert_failed || state() == s_must_replay' failed.
200630 16:35:15 [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-log
key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=1232
max_threads=4011
thread_count=172
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 41204404 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f03dc090fa8
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 = 0x7f05684eee40 thread_stack 0x49000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x55c631c21e2e]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x30f)[0x55c631632b3f]
/lib64/libpthread.so.0(+0xf600)[0x7f18e6cc4600]
/lib64/libc.so.6(gsignal+0x37)[0x7f18e5a523a7]
/lib64/libc.so.6(abort+0x148)[0x7f18e5a53a98]
/lib64/libc.so.6(+0x2f1c6)[0x7f18e5a4b1c6]
/lib64/libc.so.6(+0x2f272)[0x7f18e5a4b272]
/usr/local/mysql/bin/mysqld(+0xfbc50f)[0x55c631cc550f]
/usr/local/mysql/bin/mysqld(_Z17ha_rollback_transP3THDb+0x19b)[0x55c631635d5b]
/usr/local/mysql/bin/mysqld(_Z15ha_commit_transP3THDb+0x874)[0x55c631640fa4]
/usr/local/mysql/bin/mysqld(_Z17trans_commit_stmtP3THD+0x3f)[0x55c63152232f]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0xfb2)[0x55c631428e62]
/usr/local/mysql/bin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x15)[0x55c63138e585]
/usr/local/mysql/bin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x119)[0x55c6313968f9]
/usr/local/mysql/bin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x64c)[0x55c63139739c]
/usr/local/mysql/bin/mysqld(_ZN7sp_head7executeEP3THDb+0x997)[0x55c631392377]
/usr/local/mysql/bin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x779)[0x55c631393879]
/usr/local/mysql/bin/mysqld(+0x71730a)[0x55c63142030a]
/usr/local/mysql/bin/mysqld(+0x718b56)[0x55c631421b56]
/usr/local/mysql/bin/mysqld(_ZN12Sql_cmd_call7executeEP3THD+0x90)[0x55c631422390]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x2ab8)[0x55c63142a968]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x33c)[0x55c631430f7c]
/usr/local/mysql/bin/mysqld(+0x6169c4)[0x55c63131f9c4]
/usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x2e80)[0x55c6314345d0]
/usr/local/mysql/bin/mysqld(_Z10do_commandP3THD+0x109)[0x55c631434d79]
/usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1fa)[0x55c631513c8a]
/usr/local/mysql/bin/mysqld(handle_one_connection+0x3d)[0x55c631513d6d]
/usr/local/mysql/bin/mysqld(+0xe44dcd)[0x55c631b4ddcd]
/lib64/libpthread.so.0(+0x7e75)[0x7f18e6cbce75]
/lib64/libc.so.6(clone+0x6d)[0x7f18e5b1a8fd]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f03dc21db48):  INSERT....
Connection ID (thread ID): 775764
Status: KILL_CONNECTION
 
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 /datavolume/mariadb/maria_data
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        unlimited            unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             65536                65536                processes 
Max open files            65536                65536                files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       509775               509775               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-07-31 ]

Could this also be because implicit commit on same statement similar to MDEV-22222? If this issue can be repeated some instructions how to reproduce would be nice.

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