Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Medusa purge task not running #1121

Closed
ClusterJan opened this issue Nov 29, 2023 · 3 comments
Closed

Medusa purge task not running #1121

ClusterJan opened this issue Nov 29, 2023 · 3 comments
Assignees
Labels
bug Something isn't working done Issues in the state 'done'

Comments

@ClusterJan
Copy link

What happened?

When creating a medusa purge task, the task get's started by the k8ssandra-operator, but nothing further happens.

Did you expect to see something different?

The obsolete medusa backups should get deleted.

How to reproduce it (as minimally and precisely as possible):

Have a running K8ssandra cluster with backups that are out of the rotation and run a Purge task:

apiVersion: medusa.k8ssandra.io/v1alpha1
kind: MedusaTask
metadata:
  name: purge-backups-1
spec:
  cassandraDatacenter: kubernetes-1
  operation: purge

`

Environment

  • K8ssandra Operator version: 1.10.3
  • Cassandra version: 4.1.3
  • Medusa version: 0.16.3
  • Kubernetes version: 1.24.17

Anything else we need to know?:
Discussed in Discord.

@ClusterJan ClusterJan added the bug Something isn't working label Nov 29, 2023
@adejanovski adejanovski moved this to Assess/Investigate in K8ssandra Nov 29, 2023
@adejanovski adejanovski added the assess Issues in the state 'assess' label Nov 29, 2023
@rzvoncek
Copy link
Contributor

rzvoncek commented Dec 5, 2023

Hi @ClusterJan . I've finally managed to pick this up.
I tried to reproduce this, but I did not manage so far.

  • I've created a deployment using the versions from above (aside from the k8s version). I configured maxBackupCount to 3, created 4 backups, created a purge task, and saw the oldest backup disappear.
  • On our dogfood cluster we have about 370 backups, so I set the maxBackupCount to 369 and saw the oldest backup disappear.

I'll give it another go, but I'd like to ask for more input.

  • What's your maxBackupCount and maxBackupAge set to? You can see this either in the Medusa's config map (the one with key medusa.ini, or in the k8ssandra-operator's Medusa spec.
  • You mentioned about 16 backups have missed their deletion, but many backups are present in total?
  • I also saw the logs from the operator. I'd be also interesting to see the logs from the Medusa containers of the Cassandra pods. I'm not yet sure what precisely to look for there, so we might just need to to give it an quick look first.

@ClusterJan
Copy link
Author

Hey, thank you for taking a more in-depth look into this. Eventually, I was able to take another look as well. As it seems, the purges do work again as intended, but I'm not quite sure what could have caused this issue.

Mainly it was weird, that I wasn't able to see any confirmation of an ongoing purge in the logs, and it seemed that it might have been stuck. But I can confirm that it works in our cluster again and also syncs the medusabackups correctly as well. So I'm going to close this issue. :)

@ClusterJan ClusterJan closed this as not planned Won't fix, can't repro, duplicate, stale Dec 15, 2023
@github-project-automation github-project-automation bot moved this from Assess/Investigate to Done in K8ssandra Dec 15, 2023
@adejanovski adejanovski added done Issues in the state 'done' and removed assess Issues in the state 'assess' labels Dec 15, 2023
@adejanovski
Copy link
Contributor

Thanks for the update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working done Issues in the state 'done'
Projects
No open projects
Archived in project
Development

No branches or pull requests

3 participants