[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] howto avoid that a job is being evicted

Many thanks for this answer. This would help me much.
But I have one problem with rank.

- I use more virtuell machines than I have cpu's (this is because I want that 
all users get cpu power instantly, I will add as much cpu's as possible so 
there will be not more than 2 jobs per cpu)
-  I use default_rank to use free machines first (higher rank for vm1) 

now the question:
can I use the default_rank and a constant rank at the same time?
I use one configuration file (not shared) which is the same on each machine, 
in this I use the 
can I use know a rank=0 statement in the local configuration file at the same 

My problem is: if I use 
is then the default_rank still used?
If I understand it correct rank=0 ist the default. Therefore if 
and default_rank can be used at the same time my problem would be solved?


On Friday 03 March 2006 01:47 am, Bruce Beckles wrote:
> > do I miss something or is there any serious problem occoured? How can I
> > found out what happens?
> If you want to *COMPLETELY* disable preemption, as well as
>  	- setting PREEMPT to FALSE on each execute machine,
> you also need to
>  	- set RANK to 0 (its default) - or, in fact set RANK to any
>  	   *constant* number - on each execute machine,
> and to
>  	- set PREEMPTION_REQUIREMENTS to FALSE on your central manager.
> See Section (Disabling Preemption) in the V6.6.10 manual, or
> Section (Disabling Preemption) in the V6.7 series manual if using
> the 6.7 series:
> For Condor 6.6.10:
> 	http://www.cs.wisc.edu/condor/manual/v6.6.10/3_6Startd_Policy.html#SECTION
> For Condor 6.7:
> 	http://www.cs.wisc.edu/condor/manual/v6.7/3_6Startd_Policy.html#SECTION004
> Note that in the 6.7 series (from 6.7.1 onwards) there's a different way
> of "disabling" preemption - as described in the V6.7 manual - you just set
> a "long" MaxJobRetirementTime...
>  	-- Bruce
> P.S. By default, Condor doesn't use (or need) a "VACATE" configuration
>       file macro, so you don't need to set "VACATE =" in your
>       condor_config.local file unless (possibly) you are using it for
>       something elsewhere in your configuration files.