mariadb can't start up becaue of terminate called after throwing an instance of 'wsrep::runtime_error'

not sure "Storage Engine Memory" is the right component to file bug against, if not, please help redirect to the right owner, thanks.
The error in mariadb.log is like the following

==============================================
2023-05-20 0:08:17 0 [Note] InnoDB: Loading buffer pool(s) from /var/opt/ibm/icic/db/ib_buffer_pool
2023-05-20 0:08:17 0 [ERROR] Failed to initialize plugins.
2023-05-20 0:08:17 0 [ERROR] Aborting
terminate called after throwing an instance of 'wsrep::runtime_error'
what(): State wait was interrupted
230520 0:08:17 [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.5.16-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=8194
thread_count=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 18087694 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x3ff68002038
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 = 0x3ff94876a40 thread_stack 0x49000
/usr/libexec/mysqld(my_print_stacktrace+0x4a)[0x2aa27816a82]
/usr/libexec/mysqld(handle_fatal_signal+0x42c)[0x2aa272589fc]
[0x3ff94875c9e]
==============================================