Node got shutdown after certain period of inactivity

MySQL & MariaDB Percona XtraDB Cluster 8.x
3

Hi Matt,

I would remove all of those wsrep_provider_options except the SSL ones. Changing the EVS.* parameters away from defaults is extremely rare and not normal. Why did you set these this way?

Added those configs to avoid the very problem of shutdown. I have removed them now but the problem still persists.

Please find the logs on successful startup below:

root@ip-172-20-38-237:~# systemctl status mysql.service
● mysql.service - Percona XtraDB Cluster
     Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
     Active: activating (start-post) since Tue 2020-09-01 08:47:17 UTC; 1min 33s ago
    Process: 37543 ExecStartPre=/usr/bin/mysql-systemd start-pre (code=exited, status=0/SUCCESS)
    Process: 37595 ExecStartPre=/usr/bin/mysql-systemd check-grastate (code=exited, status=0/SUCCESS)
    Process: 37624 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 37626 ExecStartPre=/bin/sh -c VAR=`bash /usr/bin/mysql-systemd galera-recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_>
    Process: 37740 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
   Main PID: 37674 (mysqld); Control PID: 37742 (mysql-systemd)
     Status: "Server is operational"
      Tasks: 59 (limit: 4485)
     Memory: 724.6M
     CGroup: /system.slice/mysql.service
             ├─37674 /usr/sbin/mysqld --wsrep_start_position=33b6c06a-e6a7-11ea-979e-16d3d063f46c:42
             ├─37742 /bin/bash -ue /usr/bin/mysql-systemd start-post 37674
             └─38040 sleep 1


Sep 01 08:47:17 ip-172-20-38-237 systemd[1]: Starting Percona XtraDB Cluster...

It gets down after exactly 15 minutes.Please check the systemctl status:

root@ip-172-20-38-237:~# systemctl status mysql.service
● mysql.service - Percona XtraDB Cluster
     Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2020-09-01 12:00:56 UTC; 4min 40s ago
    Process: 40831 ExecStartPre=/usr/bin/mysql-systemd start-pre (code=exited, status=0/SUCCESS)
    Process: 40878 ExecStartPre=/usr/bin/mysql-systemd check-grastate (code=exited, status=0/SUCCESS)
    Process: 40907 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 40909 ExecStartPre=/bin/sh -c VAR=`bash /usr/bin/mysql-systemd galera-recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_>
    Process: 40957 ExecStart=/usr/sbin/mysqld $_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 41021 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 41023 ExecStartPost=/usr/bin/mysql-systemd start-post $MAINPID (code=exited, status=1/FAILURE)
    Process: 43786 ExecStopPost=/usr/bin/mysql-systemd stop-post (code=exited, status=0/SUCCESS)
   Main PID: 40957 (code=exited, status=0/SUCCESS)
     Status: "Server shutdown complete"


Sep 01 11:45:33 ip-172-20-38-237 systemd[1]: Starting Percona XtraDB Cluster...
Sep 01 12:00:42 ip-172-20-38-237 mysql-systemd[41023]:  ERROR!
Sep 01 12:00:42 ip-172-20-38-237 systemd[1]: mysql.service: Control process exited, code=exited, status=1/FAILURE
Sep 01 12:00:56 ip-172-20-38-237 mysql-systemd[43786]:  WARNING: mysql pid file /data/mysqld.pid empty or not readable
Sep 01 12:00:56 ip-172-20-38-237 mysql-systemd[43786]:  WARNING: mysql may be already dead
Sep 01 12:00:56 ip-172-20-38-237 systemd[1]: mysql.service: Failed with result 'exit-code'.
Sep 01 12:00:56 ip-172-20-38-237 systemd[1]: Failed to start Percona XtraDB Cluster.

Earlier I assumed that due to inactivity it is getting shutdown but every time it is getting down in 15 minutes which seems unrelated.

Is there something I am missing?