[ERROR] WSREP: FSM: no such a transition REPLICATING -> ROLLED_BACK

2022-03-24 22:44:06 8296 [ERROR] WSREP: FSM: no such a transition REPLICATING -> ROLLED_BACK
220324 22:44:06 [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.3.28-MariaDB-log
key_buffer_size=67108864
read_buffer_size=2097152
max_used_connections=134
max_threads=4098
thread_count=145
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 25335958 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7eef64000c48
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 = 0x7ef0d45c9c48 thread_stack 0x49000
/usr/libexec/mysqld(my_print_stacktrace+0x41)[0x5615bdb86251]
/usr/libexec/mysqld(handle_fatal_signal+0x4e5)[0x5615bd6b2c95]
sigaction.c:0(__restore_rt)[0x7f01d336dd50]
:0(__GI_raise)[0x7f01d1132a4f]
:0(__GI_abort)[0x7f01d1105db5]
/usr/lib64/galera/libgalera_smm.so(+0x1daf8d)[0x7f01cad6df8d]
/usr/lib64/galera/libgalera_smm.so(+0x1cfc0a)[0x7f01cad62c0a]
/usr/lib64/galera/libgalera_smm.so(+0x1ef640)[0x7f01cad82640]
/usr/libexec/mysqld(+0x721991)[0x5615bd623991]
/usr/libexec/mysqld(_Z17ha_rollback_transP3THDb+0xc2)[0x5615bd6b5da2]
/usr/libexec/mysqld(_Z14trans_rollbackP3THD+0x4d)[0x5615bd5c213d]
/usr/libexec/mysqld(_Z21wsrep_client_rollbackP3THD+0x7d)[0x5615bd63674d]
/usr/libexec/mysqld(+0x734c18)[0x5615bd636c18]
/usr/libexec/mysqld(start_wsrep_THD+0x38f)[0x5615bd6282af]
/lib64/libpthread.so.0(+0x817a)[0x7f01d336317a]
:0(_GI__clone)[0x7f01d111dd83]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7eef6400f6f0): COMMIT

Connection ID (thread ID): 8296
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,split_materialized=on

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 unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes unlimited unlimited processes
Max open files 1048576 1048576 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 2061860 2061860 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: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e