Project

General

Profile

Bug #24399

Pilot draining: add the possibility of specifying the downtime lenght

Added by Marco Mascheroni 6 months ago. Updated 22 days ago.

Status:
New
Priority:
Normal
Category:
-
Target version:
Start date:
05/12/2020
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:

CMS

Duration:

Description

In the current downtime script, a pilot that starts after the specified downtime will ignore the downtime: , https://github.com/glideinWMS/glideinwms/blob/master/creation/web_base/check_wn_drainstate.sh#L78-L79 ,

The logic is that if there is a downtime then pilots should not start, so it is probably a stale file. And in order to not waste CPUs the pilot just run normally.

A site admin using this feature was confused by this, and argued the downtime just started and pilots should have not accepted jobs. In order to be clear it would be best to specify the downtime lenght.


Related issues

Related to GlideinWMS - Bug #24401: Pilot draining: stop pilots even after the downtime timestamp has been reachedClosed05/12/2020

History

#1 Updated by Marco Mambelli 6 months ago

  • Related to Bug #24401: Pilot draining: stop pilots even after the downtime timestamp has been reached added

#2 Updated by Marco Mambelli about 1 month ago

  • Target version changed from v3_6_4 to v3_6_5

#3 Updated by Marco Mambelli 22 days ago

  • Target version changed from v3_6_5 to v3_6_6


Also available in: Atom PDF