Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] How to preempt a job for jobs with "important" set
- Date: Thu, 12 May 2011 08:37:02 -0400
- From: Ben Cotton <bcotton@xxxxxxxxxx>
- Subject: Re: [Condor-users] How to preempt a job for jobs with "important" set
Here's what we've gone at Purdue for priority jobs. This is on a
per-cluster basis not per-slot, but it should translate well.
# Prefer CMS jobs
# And prefer ones from local people more than others
RANK = (CMSJob =?= True ) * 1000 + (PriorityCMSJob =?= True) * 2500 +
(localCMSJob =?= True) * 5000
# suspend or preempt if current job isn't a CMS job and incoming one is.
# should also have the effect of not preempting CMS jobs for anything
# on these nodes
MaxJobRetirementTime = 24*3600*( RemoteUser =?= "cmsprod1@xxxxxxxxxxxxxxx" && \
( RemoteUser =?= "uscms01@xxxxxxxxxxxxxxx" || \
RemoteUser =?= "cmsprio*@rcac.purdue.edu" ) \
)
SUSPEND = ($(SUSPEND)) && ( RemoteUser =!= "cmsprod1@xxxxxxxxxxxxxxx" && \
( RemoteUser =!= "uscms01@xxxxxxxxxxxxxxx" || \
RemoteUser =!= "cmsprio*@rcac.purdue.edu" ) \
)
PREEMPT = ($(PREEMPT)) && ( RemoteUser =!= "cmsprod1@xxxxxxxxxxxxxxx" && \
( RemoteUser =!= "uscms01@xxxxxxxxxxxxxxx" || \
RemoteUser =!= "cmsprio*@rcac.purdue.edu" ) \
)
--
Ben Cotton
Systems Research Engineer
IT Research Systems
Purdue University