PXC - 8.0.27 - Crash of cluster

Hi there,
I had setup PXC 8.0.27 3 node cluster ,one of the node is crashing .
below is the log file of the crashed node.


2022-08-02T15:13:41.928699+05:30 656 [ERROR] [MY-000000] [WSREP] Percona-XtraDB-Cluster doesn't recommend using SERIALIZABLE isolation wi                          th pxc_strict_mode = ENFORCING
2022-08-02T15:16:43.075280+05:30 659 [ERROR] [MY-000000] [WSREP] Percona-XtraDB-Cluster doesn't recommend using SERIALIZABLE isolation wi                          th pxc_strict_mode = ENFORCING
2022-08-02T15:18:53.101318+05:30 670 [ERROR] [MY-000000] [WSREP] Percona-XtraDB-Cluster doesn't recommend using SERIALIZABLE isolation wi                          th pxc_strict_mode = ENFORCING
2022-08-02T16:13:11.386515+05:30 842 [ERROR] [MY-000000] [WSREP] Percona-XtraDB-Cluster prohibits use of DML command on a table (pharmara                          ckdb.test2) without an explicit primary key with pxc_strict_mode = ENFORCING or MASTER
2022-08-02T19:49:19.868719+05:30 1496 [Warning] [MY-010055] [Server] IP address '179.60.147.204' could not be resolved: Name or service n                          ot known
2022-08-02T20:10:51.865641+05:30 0 [Warning] [MY-010058] [Server] Hostname 'security.criminalip.com' does not resolve to '94.102.61.50'.
2022-08-02T22:11:24.720308+05:30 1924 [Warning] [MY-010055] [Server] IP address '205.210.31.148' could not be resolved: Name or service n                          ot known
2022-08-02T23:46:02.858332+05:30 2210 [Warning] [MY-010057] [Server] IP address '35.195.93.98' has been resolved to the host name '98.93.                          195.35.bc.googleusercontent.com', which resembles IPv4-address itself.
2022-08-02T23:46:03.054705+05:30 2211 [Warning] [MY-010057] [Server] IP address '34.77.127.183' has been resolved to the host name '183.1                          27.77.34.bc.googleusercontent.com', which resembles IPv4-address itself.
2022-08-02T23:46:03.115482+05:30 2211 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated an                          d will be removed in a future release. Please use caching_sha2_password instead'
2022-08-03T00:20:04.889271+05:30 0 [Warning] [MY-000000] [Galera] Handshake failed: http request
2022-08-03T00:32:29.571327+05:30 2351 [Warning] [MY-010055] [Server] IP address '23.225.163.211' could not be resolved: Name or service n                          ot known
2022-08-03T00:32:54.754394+05:30 2355 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated an                          d will be removed in a future release. Please use caching_sha2_password instead'
2022-08-03T05:49:09.122099+05:30 0 [Warning] [MY-000000] [Galera] Handshake failed: peer did not return a certificate
2022-08-03T05:49:10.313290+05:30 0 [Warning] [MY-000000] [Galera] Handshake failed: http request
2022-08-03T08:01:11.127375+05:30 0 [Warning] [MY-000000] [Galera] Handshake failed: unknown protocol
2022-08-03T08:01:20.978795+05:30 0 [Warning] [MY-000000] [Galera] Handshake failed: http request
2022-08-03T08:01:32.722918+05:30 0 [Warning] [MY-000000] [Galera] Handshake failed: peer did not return a certificate
2022-08-03T08:29:52.917971+05:30 3790 [Warning] [MY-010056] [Server] Host name 'ubuntu20236109.aspadmin.net' could not be resolved: Name                           or service not known
2022-08-03T09:44:50.945537+05:30 0 [Warning] [MY-000000] [Galera] Handshake failed: peer did not return a certificate
2022-08-03T09:44:52.135919+05:30 0 [Warning] [MY-000000] [Galera] Handshake failed: http request
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::sys                          tem_error> >'
  what():  remote_endpoint: Transport endpoint is not connected
2022-08-03T09:44:52.354106+05:30 0 [Note] [MY-000000] [WSREP] Initiating SST cancellation
04:14:52 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Build ID: df3732f507bb44de9b2cf240d6ec633fccedccbe
Server Version: 8.0.27-18.1 Percona XtraDB Cluster (GPL), Release rel18, Revision ac35177, WSREP version 26.4.3, wsrep_26.4.3

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 = 0 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x20d55fd]
/usr/sbin/mysqld(handle_fatal_signal+0x383) [0x1172a83]
/lib64/libpthread.so.0(+0xf630) [0x7ff48e10b630]
/lib64/libc.so.6(gsignal+0x37) [0x7ff48c3f6387]
/lib64/libc.so.6(abort+0x148) [0x7ff48c3f7a78]
/lib64/libstdc++.so.6(__gnu_cxx::__verbose_terminate_handler()+0x165) [0x7ff48cd06a95]
/lib64/libstdc++.so.6(+0x5ea06) [0x7ff48cd04a06]
/lib64/libstdc++.so.6(+0x5ea33) [0x7ff48cd04a33]
/lib64/libstdc++.so.6(+0x5ec53) [0x7ff48cd04c53]
/usr/lib64/galera4/libgalera_smm.so(+0x1dbce) [0x7ff47d545bce]
/usr/lib64/galera4/libgalera_smm.so(+0x93f48) [0x7ff47d5bbf48]
/usr/lib64/galera4/libgalera_smm.so(+0xa3dc5) [0x7ff47d5cbdc5]
/usr/lib64/galera4/libgalera_smm.so(+0xa6b6a) [0x7ff47d5ceb6a]
/usr/lib64/galera4/libgalera_smm.so(+0xaddaf) [0x7ff47d5d5daf]
/usr/lib64/galera4/libgalera_smm.so(+0x8c160) [0x7ff47d5b4160]
/usr/lib64/galera4/libgalera_smm.so(+0x1c418e) [0x7ff47d6ec18e]
/usr/lib64/galera4/libgalera_smm.so(+0x1c42b2) [0x7ff47d6ec2b2]
/lib64/libpthread.so.0(+0x7ea5) [0x7ff48e103ea5]
/lib64/libc.so.6(clone+0x6d) [0x7ff48c4beb0d]
You may download the Percona XtraDB Cluster operations manual by visiting
http://www.percona.com/software/percona-xtradb-cluster/. You may find information
in the manual which will help you identify the cause of the crash.

You have lots of issues to fix. There are many warnings in your logs about mismatch IP/hostnames. Some not even resolving (could be crash reason). You are using SERIALIZABLE which is NOT SUPPORTED. You’re attempting to use invalid DML. You are using an incorrect authentication plugin.