Re: [HTCondor-devel] Fwd: Re: [HTCondor-users] disable preemption

[Todd Tannenbaum <tannenba@xxxxxxxxxxx>]

On 7/31/2013 2:19 PM, Matthew Farrellee wrote:
> I'd say MaxJobRetirementTime fails simple - it must be configured on all
> exec nodes
Not a simple way (yet) to get around that one...

> - and fails obvious - max what what? preemption!
Definitely agree, the name choice here is unfortunate and non-obvious. 
Would be easy to give it a better name (and keep the old name as an 
alias).  Anyone have a good name idea here?

> +1 off by default, but there should be a simple and obvious way to
> enable it
Yepper....


Todd


> Best,
>
>
> matt
>
> On 07/31/2013 03:16 PM, Todd Tannenbaum wrote:
> > On 7/31/2013 2:07 PM, Matthew Farrellee wrote:
> > > This question comes up so often, there should really be a single,
> > > obvious configuration change to make...
> > Yes. There is one. It is called MaxJobRetirementTime.  The problem is
> > prior to v8.0, there were nasty side effects of using
> > MaxJobRetirementTime. These were fixed in v7.9.6 - see
> >    https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=3539
> >
> > So now the imo the best wisdom I tell folks is simply use
> > MaxJobRetirementTime if using v8.0 or above.
> >
> > For v8.1, I think we should have preemption disabled by default.  I.e.
> > folks should opt-in to enable preemption. Thoughts?
> >
> > Todd
> >
> >
> >
> > > -------- 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.

--
Todd Tannenbaum <tannenba@xxxxxxxxxxx> University of Wisconsin-Madison
Center for High Throughput Computing   Department of Computer Sciences
HTCondor Technical Lead                1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132                  Madison, WI 53706-1685