Openshift 4.12 (kubernetes 1.25) Operator version is 1.12 (we’re about to upgrade to 1.13) {"log":"2023-11-20T17:22:01.850635Z 0 [Note] [MY-012487] [InnoDB] DDL log recovery : begin\n","file":"/var/lib/mysql/wsrep_recovery_verbose.log"} {"log":"2023-11-20T17:22:01.850973Z 0 [Note] [MY-012488] [Inn…

The elegant approach is to run up a debug pod against the failing pxc pod and delete the galera.cache file. When the container restarts, an SST will get initiated.

One of the pxc pods is getting OOM Killed on startup (and I assume recovery)

MySQL & MariaDB Percona XtraDB Cluster 8.x

mtye November 24, 2023, 4:44pm 4

After some further investigation, it looks like I’m suffering from this bug here - GCache::RingBuffer initial scan dies at 0.0% · Issue #624 · codership/galera · GitHub

Is the correct procedure here to delete the pod and PVC which will force an SST ?

Thanks

Percona XtraDB Node not able to start up - k8s

Topic		Replies	Views
Fresh instance with Percona XtraDB Cluster Operator v1.8.0 not starting completly under OKD Percona Operator for MySQL	26	6820	March 24, 2023
Memory management and RAM OOM kill for PXC pods Percona Operator for MySQL mysql , percona	16	2917	September 1, 2022
Unable to Restore PXC Percona Operator for MySQL mysql	5	1413	July 10, 2023
I am getting CrashLookBackOff error for Percona XtraDB Cluster 8.0.20 in Kubernetes Percona Distribution for MySQL percona	8	2749	November 17, 2020
Random pxc node fails with gcomm issues Percona Operator for MySQL mysql , percona	7	1131	January 12, 2023

One of the pxc pods is getting OOM Killed on startup (and I assume recovery)

Related Topics