Project

General

Profile

Bug #19055

runcible should support generate applicability call for single consumer

Added by Chris Duryee over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Currently, runcible only supports making an applicability regen call where all of the UUIDs are passed in via POST. This works, but due to the way Pulp works, all of these calls get 'pinned' to the same worker. For example, if you make six calls with six different UUIDs (example: "[A]", "[B]", "[C]", ...), all six of these will get pinned to the same worker. This can make applicability regen very slow.

If you call the applicability regen differently, the call does not get pinned to a worker. See https://pulp.plan.io/issues/1173#note-12 for more detail.

Associated revisions

Revision 2de23838 (diff)
Added by Chris Duryee over 5 years ago

Fixes #19055 - add new call for generate applicability

The previous applicability call would 'lock' on a single worker. This call does
not pin to a single worker, so applicability regeneration can spread across all
workers.

Note that this does not change any functionality, it just exposes a new call
for use by Katello.

History

#1 Updated by Chris Duryee over 5 years ago

  • Pull request https://github.com/Katello/runcible/pull/189 added

#2 Updated by Chris Duryee over 5 years ago

  • Status changed from New to Closed

PR is merged, marking as closed

Also available in: Atom PDF