Project

General

Profile

Bug #12975

Held Status Confusion: Label job as completed or not?

Added by Tyler Propp about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
06/21/2016
Due date:
% Done:

100%

Estimated time:
First Occurred:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

At the following page: https://pomsgpvm01.fnal.gov/poms/triage_job?job_id=284315&tmin=2016-06-20%2019:34:00
Towards the bottom for job history, POMS is confused on the status of the job, switching from "completed" to "held" a few dozen times. Being the job is quite old and has been held for a good long time, there should be an easy way to clear this up.

History

#1 Updated by Marc Mengel about 3 years ago

  • Target version set to v1_0_0

#2 Updated by Marc Mengel about 3 years ago

After some discussion at the POMS meeting, we decided we should terminate held jobs, as the recovery mechanism is the right way to handle failures, and SAM projects are not gong to re-deliver the files that caused the resource overrun without a recovery job anyway. This should be only a few lines of code, as we already know how to kill a job, and we just have to call it when we get an update to mark it Held...

#3 Updated by Marc Mengel almost 3 years ago

  • Status changed from New to Closed

#4 Updated by Marc Mengel almost 3 years ago

  • % Done changed from 0 to 100


Also available in: Atom PDF