You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened?
After upgrading K8ssandra-operator from 1.7.0 to 1.16.0 I noticed periodic restarts of k8ssandra-operator due to memory leak.
It happened twice right after failed MedusaBackupJob
What happened?
After upgrading K8ssandra-operator from 1.7.0 to 1.16.0 I noticed periodic restarts of k8ssandra-operator due to memory leak.
It happened twice right after failed MedusaBackupJob
MedusaBackupJob failed because of POD OOM restart (we are using pretty small instances on
test
env)Also MedusaBackupSchedule is not working after failed backup - not creating new MedusaBackupJobs
Did you expect to see something different?
Failed backup should not affect operator and next backups.
How to reproduce it (as minimally and precisely as possible):
I think killing one POD during the backup should work
K8ssandra Operator version: 1.16.0
Kubernetes version information: 1.29
Kubernetes cluster kind: GKE
K8ssandra Operator Logs: I see a lot of
MedusaBackupJob is still being processed
INFO messagesThe text was updated successfully, but these errors were encountered: