[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Condor configuration question
- Date: Tue, 06 Jan 2009 11:46:36 -0600 (CST)
- From: Steven Timm <timm@xxxxxxxx>
- Subject: Re: [Condor-users] Condor configuration question
2 ways to do it
a) here is a preemption requirements statement much like
the UWCS default one.
[root@fcdf2x1 ~]# condor_config_val PREEMPTION_REQUIREMENTS
(((CurrentTime - EnteredCurrentState) > (1 * (10 * 60)) && RemoteUserPrio
SubmittorPrio * 1.2) && RemoteUser =!= "cdf@xxxxxxxx" && RemoteUser =!=
"cdffgrid@xxxxxxxx" && RemoteUser =!= "cdfnam@xxxxxxxx" && RemoteUser =!=
All you have to do is to up the timestamp from more than 600 seconds,
as above, to however much time you want in seconds.
Second thing you can do is to use nonzero maxjobretirementtime
so things will still pre-empt but it will still have maxjobretirementtime
seconds to finish the job.
For both of the scenarios above machine RANK should be set to zero.
On Tue, 6 Jan 2009, Balamurali Ananthan wrote:
Wondering if it is possible to configure condor in such a way that, a remote
user's job should not be preempted before a certain time is elapsed.
For example, userx submits a job that runs for more-or-less 10 hours. I want
to configure condor in such a way that the job once started on an execute
machine, should not be disturbed for 11 hours.
If this is possible, could someone please point me to the right
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:
Steven C. Timm, Ph.D (630) 840-8525
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.