Galera crashes with "WSREP: FSM: no such a transition REPLICATING -> COMMITTED"

2020-11-02 15:51:10 682745 [ERROR] WSREP: FSM: no such a transition REPLICATING -> COMMITTED

201102 15:51:10 [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.14-MariaDB-log

key_buffer_size=33554432

read_buffer_size=2097152

max_used_connections=737

max_threads=4011

thread_count=700

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 41352608 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fcbfcfa1ec8

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 = 0x7fd944857e40 thread_stack 0x49000

*** stack smashing detected ***: /usr/local/mysql/bin/mysqld terminated

Fatal signal 11 while backtracing