Project

Profile

Help

Issue #1173

closed

Content Applicability Regeneration for individual consumers is sent to a single worker

Added by dkliban@redhat.com over 8 years ago. Updated almost 5 years ago.

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

Description

The same tags are used when calculating applicability for a single consumer [0] as for all consumers bound to a specific repo [1]. As a result when multiple consumers are registered within a short amount of time, the tasks to generate content applicability profiles for these consumers are sent to a single worker and the tasks are executed serially.

[0] https://github.com/pulp/pulp/blob/2.6-dev/server/pulp/server/webservices/controllers/consumers.py#L642
[1] https://github.com/pulp/pulp/blob/86b154a74e7fac73ecd54021cf2730b522db0588/server/pulp/server/webservices/views/repositories.py#L983

Also available in: Atom PDF