truncate is crashing mariadb galera cluster slave nodes

Slaves are going to wsrep_ready off state and 'show full processlist' shows 'truncate'. This happened until we replaced 'truncate custom_apps_rules_pending' with 'DELETE FROM custom_apps_rules_pending'

2020-10-20 14:36:16 20 [Note] WSREP: MDL BF-BF conflict

schema:  tenant7481db

request: (20    seqno 2374236798        wsrep (high priority, exec, executing) cmd 0 161        DELETE a

            FROM custom_apps a

            LEFT JOIN custom_apps_rules r USING (app_id)

            WHERE r.rule_id IS NULL��~N_^S^A)

granted: (53    seqno 2374236797        wsrep (toi, exec, committed) cmd 0 8    TRUNCATE `custom_apps_rules_pending`)

2020-10-20 14:36:16 20 [ERROR] Aborting

Error log output
===========

2020-10-20 15:57:41 0 [Warning] WSREP: server: mariadb02 unallowed state transition: disconnecting -> disconnecting

mysqld: /home/buildbot/buildbot/build/mariadb-10.4.7/wsrep-lib/src/server_state.cpp:1296: void wsrep::server_state::state(wsrep::unique_lock<wsrep::mutex>&, wsrep::server_state::state): Assertion `0' failed.
201020 15:57:41 [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.7-MariaDB-1:10.4.7+maria~xenial-log
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=243
max_threads=50002
thread_count=76
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 110050057 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56049b4c7f4e]
/usr/sbin/mysqld(handle_fatal_signal+0x307)[0x56049af5bb07]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fd074634390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7fd0739ff428]
linux/raise.c:54(__GI_raise)[0x7fd073a0102a]
stdlib/abort.c:91(__GI_abort)[0x7fd0739f7bd7]
assert/assert.c:92(__assert_fail_base)[0x7fd0739f7c82]
/usr/sbin/mysqld(_ZN5wsrep12server_state5stateERNS_11unique_lockINS_5mutexEEENS0_5stateE+0x77d)[0x56049b55fa0d]
/usr/sbin/mysqld(_ZN5wsrep12server_state10disconnectEv+0x57)[0x56049b55faf7]
/usr/sbin/mysqld(_Z26wsrep_shutdown_replicationv+0xba)[0x56049aec0b8a]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1bb5)[0x56049ac8b295]
csu/libc-start.c:325(__libc_start_main)[0x7fd0739ea830]
/usr/sbin/mysqld(_start+0x29)[0x56049ac7d129]
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...