This question comes up so often, there should really be a single,
obvious configuration change to make...
-------- Original Message --------
Subject: Re: [HTCondor-users] disable preemption
Date: Wed, 31 Jul 2013 11:38:35 -0400
From: Ben Cotton <ben.cotton@xxxxxxxxxxxxxxxxxx>
Reply-To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Have you taken a look at the section in the manual?
http://research.cs.wisc.edu/htcondor/manual/v7.8/3_5Policy_Configuration.html#SECTION00459500000000000000
Specifically:
#Disable preemption by machine activity.
PREEMPT = False
#Disable preemption by user priority.
PREEMPTION_REQUIREMENTS = False
#Disable preemption by machine RANK by ranking all jobs equally.
RANK = 0
#Since we are disabling claim preemption, we
# may as well optimize negotiation for this case:
NEGOTIATOR_CONSIDER_PREEMPTION = False
There are several ways HTCondor may preempt a job, so you'll want to
make sure you cover all the bases.
--
Ben Cotton
Senior Support Engineer
Cycle Computing, LLC
The Leader in Utility Supercomputing Software
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/
|