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

RE: [Condor-users] How to have schedd drop claim after each job

lovely - thank you.


> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of Dan Bradley
> Sent: 21 July 2004 16:00
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] How to have schedd drop claim 
> after each job


> >Machine ranks a job higher than an existing one - relative 
> user prio immaterial 
> >-> timeout 
> >: Unclaimed
> >
> >It is this last one that is critical to me - if it only 
> works if the user prio is higher then it's not much use to 
> preform job rather than user allocation policies...
> >
> Exactly.  Since the retirement time is a part of the _machine_ policy 
> rather than the negotiator policy, it applies even in case of startd 
> rank preemption, unlike PREEMPTION_REQUIREMENTS.  Whatever retirement 
> time you configure (could be specific to the types of jobs 
> the machines 
> prefer), it applies in this case as well.  Once the job 
> vacates, the new 
> claim replaces the old one.

Gloucester Research Limited believes the information 
provided herein is reliable. While every care has been 
taken to ensure accuracy, the information is furnished 
to the recipients with no warranty as to the completeness 
and accuracy of its contents and on condition that any 
errors or omissions shall not be made the basis for any 
claim, demand or cause for action.