Re: [Condor-users] High vs. low priority jobs

["Mueller, Eike" <eike.mueller@xxxxxxxxxxxxxxxx>]

Hi Ben,

thanks for you reply, I've tried what you suggested but must be doing
something wrong. This is what I have in my
/etc/condor/condor_config.local:

---- condor_config.local start
------------------------------------------------------------------------
----

##  What machine is your central manager?

CONDOR_HOST = $(FULL_HOSTNAME)

## Pool's short description

COLLECTOR_NAME = Personal Condor at $(FULL_HOSTNAME)

##  When is this machine willing to start a job? 

START = TRUE

# Prefer doubletake jobs
RANK = ( DoubletakeJob )*9000

# suspend or preempt if current job isn't a doubletake job and
# incoming one is.  Should also have the effect of not preempting
# doubletake jobs for anything on these nodes
MaxJobRetirementTime = 24*3600*( DoubletakeJob )

##  When to suspend a job?

##SUSPEND = FALSE
##SUSPEND = TRUE
SUSPEND = ($(SUSPEND)) && ( DoubletakeJob =!= True )

##  When to nicely stop a job?
##  (as opposed to killing it instantaneously)

##PREEMPT = FALSE
##PREEMPT = TRUE
PREEMPT = ($(PREEMPT)) && ( DoubletakeJob =!= True )

##  When to instantaneously kill a preempting job
##  (e.g. if a job is in the pre-empting stage for too long)

KILL = FALSE

##  This macro determines what daemons the condor_master will start and
keep its watchful eyes on.
##  The list is a comma or space separated list of subsystem names

DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD

##  Sets how often the condor_negotiator starts a negotiation cycle. 
##  It is defined in seconds and defaults to 60 (1 minute). 

NEGOTIATOR_INTERVAL = 20

##  Disable UID_DOMAIN check when submit a job

TRUST_UID_DOMAIN = TRUE

---- condor_config.local end
------------------------------------------------------------------------
------

The submission scripts for my Research (low priority) and Emergency
Response (high priority, needs to run immidiately) jobs are:

---- submit.Research start
------------------------------------------------------------------------
--------

#####################################################
# Submit description file for program Research.exe
#####################################################
Executable   = Research.exe
Universe     = standard
Output       = /dev/null
Log          = /dev/null
Notification = Never

Queue 5

---- submit.Research end
------------------------------------------------------------------------
----------

---- submit.Emergency start
------------------------------------------------------------------------
-------

#####################################################
# Submit description file for program Emergency.exe
#####################################################
Executable   = Emergency.exe
Universe     = vanilla
Output       = /dev/null
Log          = /dev/null
Notification = Never
+DoubletakeJob = True

Queue 1

---- submit.Emergency end
------------------------------------------------------------------------
---------

If I do a condor_submit submit.Research followed by
condor_submit.Emergency, the research jobs keep running happily and do
not get premeempted.

Thanks,

Eike




-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ben Cotton
Sent: 28 September 2010 16:57
To: Condor-Users Mail List
Subject: Re: [Condor-users] High vs. low priority jobs

Elke,

We're doing something similar of a few of our clusters at Purdue.
Here's the config we use on the startd side:

# Prefer doubletake jobs
RANK = ( DoubletakeJob )*9000

# suspend or preempt if current job isn't a doubletake job and
# incoming one is.  Should also have the effect of not preempting
# doubletake jobs for anything on these nodes
MaxJobRetirementTime = 24*3600*( DoubletakeJob )

SUSPEND    = ($(SUSPEND)) && ( DoubletakeJob =!= True )
PREEMPT    = ($(PREEMPT)) && ( DoubletakeJob =!= True )

And then on the submit side, we have:

# Set a ClassAd for jobs submitted from here to use in premption
DoubletakeJob = True
SUBMIT_EXPRS = $(SUBMIT_EXPRS),DoubletakeJob

This means every job from this submitter gets marked as a Doubletake
job (which is appropriate for our setup).  If you're submitting both
priority and non-priority jobs from the same submitter, you can add a
line like such to your submit file

+DoubletakeJob = True


Hope this helps!
BC

-- 
Ben Cotton
Systems Research Engineer
IT Research Systems
Purdue University
_______________________________________________
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:
https://lists.cs.wisc.edu/archive/condor-users/