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?
Created some backups using MedusaBackupSchedule CRD, and created a MedusaTask CRD with "operation: purge" to remove old backups based on max_backup_age & max_backup_count configurations.
Did you expect to see something different?
All old backups should get removed as per max_backup_age & max_backup_count configurations. But could see some backups still present in Minio and all the backups present are having a common file "bti-Rows.db" with size 0.
How to reproduce it (as minimally and precisely as possible):
Create backup using k8ssandra-operator and ensure that there is SSTables with size 0 or empty files. Run the MedusaTask to purge old backups and observe Minio.
What happened?
Created some backups using MedusaBackupSchedule CRD, and created a MedusaTask CRD with "operation: purge" to remove old backups based on max_backup_age & max_backup_count configurations.
Did you expect to see something different?
All old backups should get removed as per max_backup_age & max_backup_count configurations. But could see some backups still present in Minio and all the backups present are having a common file "bti-Rows.db" with size 0.
How to reproduce it (as minimally and precisely as possible):
Create backup using k8ssandra-operator and ensure that there is SSTables with size 0 or empty files. Run the MedusaTask to purge old backups and observe Minio.
Environment
used Minio for storing the backups, followed https://docs.k8ssandra.io/tasks/backup-restore/
Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.1
Minio contents of one of the Cassandra nodes:
Medusa sidecar container logs showing Purging operation removing all files except "bti-Rows.db"
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-23
The text was updated successfully, but these errors were encountered: