Project

General

Profile

Feature #23342

Stop considering held limits when counting maximum jobs

Added by Marco Mascheroni about 2 months ago. Updated 4 days ago.

Status:
Resolved
Priority:
Normal
Category:
-
Target version:
Start date:
09/26/2019
Due date:
% Done:

0%

Estimated time:
Stakeholders:

Factory Ops

Duration:

Description

Factory ops struggled keeping the pressure in Syracuse. A lot of pilots are going held when they claim the opportunistic resource back. Would like to not consider the held here:

<per_entry glideins="10000" held="1000" idle="4000"/>

In practice this goes from:

can_add = max_glideins > running + held + idle

to
can_add = max_glideins > running + idle

History

#1 Updated by Marco Mascheroni about 2 months ago

  • Stakeholders updated (diff)

#2 Updated by Marco Mascheroni 14 days ago

  • Assignee changed from Marco Mascheroni to Marco Mambelli

#3 Updated by Marco Mascheroni 14 days ago

  • Status changed from New to Feedback

#4 Updated by Marco Mambelli 13 days ago

  • Assignee changed from Marco Mambelli to Marco Mascheroni

max held has been removed from all the cumulative limits and it seems is not checked individually.
Is the factory stopping submission if going above max_held?
It should be checked separately if it is no more in the total

#5 Updated by Marco Mascheroni 7 days ago

  • Status changed from Feedback to Resolved

#6 Updated by Marco Mambelli 4 days ago

  • Tracker changed from Bug to Feature


Also available in: Atom PDF