Delay publication file deletion to orphan cleanup to aid in online backups
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @jlsherrill (jsherril@redhat.com)
Redmine Issue: 8852, https://pulp.plan.io/issues/8852
It would be useful if we could:
- perform an online backup of the pulp postgresql database, this is relatively quick
- backup the /var/lib/pulp/ filesystem
This is nearly possible today as we could simply not run orphan cleanup. However publication files (such as repomd files for yum content), are cleaned up when a publication is deleted. It would be awesome to defer that until orphan cleanup time. This would allow /var/lib/pulp/ to be additive until orphan cleanup is called.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where publication files are deleted and where orphan cleanup runs. Verify the online PostgreSQL backup followed by filesystem backup workflow, and consider the work done when publication files remain available until orphan cleanup is invoked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100