Project

General

Profile

Actions

Feature #20661

closed

Job invocations should have a priority

Added by Ivan Necas over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
-
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1386283

Description of problem:

Every job should have a priority so that if there are enqueued jobs the new jobs with higher priority are executed first.

For instance:

1- There are 100 reposync jobs currently running. There are another 50 jobs waiting to run because the capsules cannot run all of them concurrently.

2- Some errata is published and the customer wants to immediately apply it. The customer should be able to apply a higher priority to the "apply errata" jobs. Therefore, the reposync jobs that are queued will only run after the errata jobs have finished.


Related issues 1 (0 open1 closed)

Blocked by foreman-tasks - Bug #22885: Add support for multipile queues in dynflowClosed03/13/2018Actions
Actions #1

Updated by Ivan Necas over 6 years ago

  • Blocked by Bug #22885: Add support for multipile queues in dynflow added
Actions #2

Updated by The Foreman Bot over 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ivan Necas
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/330 added
Actions #3

Updated by Ivan Necas over 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF