Project

Profile

Help

Issue #6498

closed

orphan cleanup does not prevent other tasks from starting after it starts running

Added by dkliban@redhat.com about 4 years ago. Updated about 4 years ago.

Status:
CLOSED - WORKSFORME
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Orphan clean up task is dispatched without reservations[0]. This creates a race condition between orphan_cleanup and repository version creation tasks.

[0] https://github.com/pulp/pulpcore/blob/master/pulpcore/app/views/orphans.py#L20

Actions #1

Updated by dkliban@redhat.com about 4 years ago

  • Status changed from NEW to CLOSED - WORKSFORME

I was not able to actually reproduce this race condition. The resource manager executes the orphan cleanup task and does not handle any other tasks until orphan cleanup is done.

Also available in: Atom PDF