Rollback crashes active nodes in galera cluster

2021-02-09  8:23:32 1960824 [ERROR] WSREP: FSM: no such a transition ROLLED_BACK -> ROLLED_BACK

210209  8:23:32 [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.25-MariaDB-log

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=559

max_threads=602

thread_count=291

It is possible that mysqld could use up to

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

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

Thread pointer: 0x7f4a348bc4b8

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

terminate called after throwing an instance of 'gu::Exception'

  what():  gu_mutex_destroy(): 16 (Device or resource busy)

         at galerautils/src/gu_mutex.hpp:~Mutex():32

2021-02-09  8:23:30 1960770 [ERROR] WSREP: FSM: no such a transition ROLLED_BACK -> ROLLED_BACK

210209  8:23:30 [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.25-MariaDB-log

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=563

max_threads=602

thread_count=294

It is possible that mysqld could use up to

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

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

Thread pointer: 0x7f3b08218728

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...

2021-02-09  8:23:30 1960773 [ERROR] WSREP: FSM: no such a transition ROLLED_BACK -> ROLLED_BACK