Project

Profile

Help

Story #8852

Delay publication file deletion to orphan cleanup to aid in online backups

Added by jsherril@redhat.com 4 months ago. Updated 4 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Quarter:

Description

It would be useful if we could:

  1. perform an online backup of the pulp postgresql database, this is relatively quick
  2. 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.

History

#1 Updated by bmbouter 4 months ago

I'd like to see this improve so +1 to this effort.

I have these concerns about the proposal (although I like the idea sharing):

  1. Other users may rely on this functionality and we probably couldn't adjust this with Pulp3 being released for so long.
  2. How can we find a solution that also serves users who want online backups but can't "hold back" the orphan cleanups?

Can more info be shared about the problems with an LVM snapshot approach? I've always heard that's the answer, but maybe in practice it's not that simple.

#2 Updated by dkliban@redhat.com 4 months ago

  • Tracker changed from Issue to Story
  • % Done set to 0
  • Severity deleted (2. Medium)
  • Triaged deleted (No)

#3 Updated by jsherril@redhat.com 4 months ago

Evgeni was the one that shared the issues, essentially what it sounded like was that once you have a snapshot created, write performance drops considerably.

I found a blog post that details this: https://www.percona.com/blog/2009/02/05/disaster-lvm-performance-in-snapshot-mode/

Please register to edit this issue

Also available in: Atom PDF