09:53:59 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.

Build ID: 5a2199b1784b967a713a3bde8d996dc517c41adb
Server Version: 8.0.21-12.1 Percona XtraDB Cluster (GPL), Release rel12, Revision 4d973e2, WSREP version 26.4.3, wsrep_26.4.3

Thread pointer: 0x7fc4b83c8510
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 = 7fc4fc0aad90 thread_stack 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x20b4cf1]
/usr/sbin/mysqld(handle_fatal_signal+0x3c3) [0x128c8e3]
/lib64/libpthread.so.0(+0x12b20) [0x7fc5378d3b20]
/usr/lib64/galera4/libgalera_smm.so(+0x1e36e7) [0x7fc5298a36e7]
/usr/lib64/galera4/libgalera_smm.so(+0x1fdd21) [0x7fc5298bdd21]
/usr/sbin/mysqld(wsrep::wsrep_provider_v26::replay(wsrep::ws_handle const&, wsrep::high_priority_service*)+0x3c) [0x27ff33c]
/usr/sbin/mysqld(Wsrep_client_service::replay()+0xb7) [0x129a737]
/usr/sbin/mysqld(wsrep::transaction::after_statement()+0x23d) [0x27fd6ad]
/usr/sbin/mysqld(wsrep::client_state::after_statement()+0x12d) [0x27e0b1d]
/usr/sbin/mysqld(ha_commit_trans(THD*, bool, bool)+0xa93) [0xe4c2b3]
/usr/sbin/mysqld(trans_commit_stmt(THD*, bool)+0x47) [0x1250ff7]
/usr/sbin/mysqld(mysql_execute_command(THD*, bool)+0x5631) [0x1135801]
/usr/sbin/mysqld(Prepared_statement::execute(String*, bool)+0x919) [0x1169be9]
/usr/sbin/mysqld(Prepared_statement::execute_loop(String*, bool)+0xb4) [0x116c5d4]
/usr/sbin/mysqld(mysqld_stmt_execute(THD*, Prepared_statement*, bool, unsigned long, PS_PARAM*)+0x191) [0x116dc01]
/usr/sbin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x2ae0) [0x113c3d0]
/usr/sbin/mysqld(do_command(THD*)+0x27f) [0x113da2f]
/usr/sbin/mysqld() [0x127c888]
/usr/sbin/mysqld() [0x25d49f8]
/lib64/libpthread.so.0(+0x814a) [0x7fc5378c914a]
/lib64/libc.so.6(clone+0x43) [0x7fc535666f23]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED