mariadb1_uat

2021-06-22 12:35:02 11 [Note] WSREP: cluster conflict due to high priority abort for threads:
2021-06-22 12:35:02 11 [Note] WSREP: Winning thread:
   THD: 11, mode: applier, state: executing, conflict: no conflict, seqno: 89327026
   SQL: DELETE FROM blobs WHERE id = '7432858'öØÑ`^S^F
2021-06-22 12:35:02 11 [Note] WSREP: Victim thread:
   THD: 15, mode: applier, state: idle, conflict: no conflict, seqno: 89327028
   SQL: NULL
2021-06-22 12:35:02 0 [ERROR] WSREP: Trx 89327026 tries to abort slave trx 89327028. This could be caused by:
        1) unsupported configuration options combination, please check documentation.
        2) a bug in the code.
        3) a database corruption.
 Node consistency compromized, need to abort. Restart the node to resync with cluster.
210622 12:35:02 [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.29-MariaDB-1:10.3.29+maria~bionic-log
key_buffer_size=134217728
read_buffer_size=134217728
max_used_connections=26
max_threads=1002
thread_count=24
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 262821945 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 0x12c00000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x560ee4349b8e]
/usr/sbin/mysqld(handle_fatal_signal+0x515)[0x560ee3dde8c5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12980)[0x7f9ca6c54980]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f9ca688ffb7]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f9ca6891921]
/usr/sbin/mysqld(+0x90a914)[0x560ee3f68914]
/usr/sbin/mysqld(+0x90f83c)[0x560ee3f6d83c]
/usr/sbin/mysqld(handle_manager+0x1f3)[0x560ee3bf0a83]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7f9ca6c496db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f9ca697271f]
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 /srv/galera-uat/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        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             15430                15430                processes
Max open files            4096                 4096                 files
Max locked memory         67108864             67108864             bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       15430                15430                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/share/apport/apport %p %s %c %d %P %E