Project

General

Profile

Feature #14008

Treat Disconnect and Job Failure Differently

Added by Alexander Himmel about 3 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
10/03/2016
Due date:
% Done:

0%

Estimated time:
Duration:

Description

A thought I've had as we try to move more of our processing off-site. Many OSG sites will disconnect a job if priorities on the site change, and then put the job back in the queue, the logic on Condor's mind being that a job will do the same thing every time it runs, so putting it back in the queue is the equivalent of trying again. However with a SAM project, the file the job was working on when it was evicted is just marked "skipped" and never re-tried. Would it be possible to try to flag these disconnects and have SAM put the file back in the queue of files to be processed?

This is not a pressing request, obviously, but something to turn over in your mind to better get the different FIFE tools working together.

History

#1 Updated by Robert Illingworth about 3 years ago

I've already been thinking along these lines. Putting them back in the queue is doable, but complex. And there are other issues, like how do we even detect that condor has preempted a job? So it's something we're already thinking about, but it's been lower down the priorities.



Also available in: Atom PDF