SolrBackup should call DELETEBACKUP with purgeUnused=true
- Dominant language
- Go
- Stars
- 283
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
When keeping only the most recent n backups, orphaned files can accumulate in the backup repository. Calling
/solr/admin/collections?action=DELETEBACKUP&name=myBackupName&location=/path/to/my/shared/drive&purgeUnused=true will clean those up. See https://solr.apache.org/guide/solr/latest/deployment-guide/collection-management.html for documentation on this api call.
The SolrBackup CRD should call this api as part of managing recurring backups.
This was part of the original plan in #359 but it was abandoned due to a bug with that api which has since been fixed. Details are in #359's comment threads.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the SolrBackup CRD's recurring-backup management and review the DELETEBACKUP API documentation linked in the issue. Read the discussion in #359 for the prior implementation context, then verify that retaining only the newest backups also removes orphaned repository files with purgeUnused=true.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, search
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100