Project

General

Profile

Feature #11756

Is it time to get rid of TotalTimeUnclaimedIdle?

Added by Parag Mhashilkar over 3 years ago. Updated 18 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
02/17/2016
Due date:
% Done:

0%

Estimated time:
Stakeholders:

CMS

Duration:

Description

In case of busy pool, like in cms, negotiation cycles could be quite long. At times it is possible that a resource may not be considered at all for match making if the cycle runs long enough and triggers max allowed time for the cycle. In such cases it is quite easy for the existing idle glideins to trigger TotalTimeUnclaimedIdle after their first job run.
One of the options was to remove the TotalTimeUnclaimedIdle and only shutdown a glidein based on idle time since it entered idle state.

There is always a possibility that pre-emption would play badly with this. We need to investigate it if this becomes a priority.

History

#1 Updated by Marco Mambelli over 1 year ago

  • Target version changed from v3_2_x to v3_4_x

#2 Updated by Marco Mambelli about 1 year ago

  • Target version changed from v3_4_x to v3_5_x

#3 Updated by Marco Mambelli 18 days ago

  • Target version changed from v3_5_x to v3_6_x


Also available in: Atom PDF