[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Disabling the restarting of jobs
- Date: Fri, 29 Feb 2008 11:27:47 -0600
- From: Dan Bradley <dan@xxxxxxxxxxxx>
- Subject: Re: [Condor-users] Disabling the restarting of jobs
In the submit file:
periodic_hold = NumJobStarts > 1
There is no way to update the hold reason, unfortunately. However, it
will state that the above expression evaluated to true, which will
hopefully be self explanatory.
Robert E. Parrott wrote:
We have a certain set of users whose parallel code is fairly strict
in the way it names and manages files. They are looking for an option
to disable the restarting of jobs after the jobs have been damaged
(for example by an OOM condition on a node), because a restarted job
will otherwise overwrite the partial, and still usable, data files.
Is there a submit file expression, of a config expression, with a
boolean to be added to the config file, that would put all jobs that
would otherwise restart into a "hold" state?
As a secondary question, would there be a way to update the
"HoldReason" classad expression with something relevant?
Robert E. Parrott, Ph.D. (Phys. '06)
Associate Director, Grid and
Project Manager, CrimsonGrid Initiative
Harvard University Sch. of Eng. and App. Sci.
33 Oxford St.
Cambridge, MA 02138
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: