Re: [Condor-users] Specifying Max Job Run Time

[Steven Timm <timm@xxxxxxxx>]

Perhaps one  way is to set the priority of jobs that have run
a very long time to a very low value so they will get pre-empted
by almost anything.

Steve

On Mon, 23 Oct 2006, Terrence Martin wrote:

> I do not suppose there is a recipe out there for restricting how long a
> job runs while at the same time making sure that jobs are not
> interrupted prior to that run time and for the long run jobs only to be
> kicked if there are other jobs waiting for the queue? Say a value of 72
> hours, that is both the min and max runtime for jobs but if the jobs are
> the only one on the cluster that they can just keep running.
>
> There are a lot of settings it seems, from PREEMPTION_REQUIREMENTS to
> MaxJobRetirementTime to PREEMPT_LATENCY. It is just not all that clear
> to me how to go about getting all these settings to do what I want as
> far as putting an upper limit on jobs after which they can not be
> guaranteed to run, while at the same time not kicking off jobs that may
> be running long for legitimate reasons on an otherwise underused cluster.
>
> Terrence
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR

--
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525  timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team