Re: [Condor-users] jobs match, but prefer another specific job despite its worse user-priority

[Harald van Pee <pee@xxxxxxxxxxxxxxxxx>]

I believe CLAIM_WORKLIFE
can help here
http://www.cs.wisc.edu/condor/manual/v6.8/3_3Configuration.html#13095

If I understand this correct, than a 
CLAIM_WORKLIFE = 120
will keep a claim reserved for 120s if a job finishes faster the claim is 
still open and the user can start another job. 

But here we still see that a user with the lowest priority can use a couple of 
machines with 16 virtuell machines for hours even with jobs running longer 
than 10 minutes 
and CLAIM_WORKLIFE = 120 set
and high priority user can not get  any of them.

Can someone explain such a behaviour?

Harald

On Thursday 17 January 2008 03:03 am, Frazer, Durban A wrote:
> How can I setup condor so that the user with the better priority always
> gets to run their job first?
>
>
>
>
>
> We have a problem where:
>
>
>
> User A submits 100s of jobs and fills the pool repeatedly.
>
> After user A submits another set of jobs to the pool, user B submits
> their first job.
>
> After user B submits their job, but while all servers are busy, user  A
> submits another batch of jobs.
>
>
>
> User A's first set of jobs will complete, and her second set of jobs
> will start, and user B's job will not start.
>
>
>
> Running condor_analyze on user B's job shows:
>
>
>
> 8 match, but prefer another specific job despite its worse user-priority
>
>
>
>
>
> Why is user A able to continue to get their jobs to start, even though
> user B has a better priority?
>
>
>
> How can I change this so that the user with the better priority always
> gets to run their job first?
>
>
>
>
>
>
>
> We are using condor 6.7.19
>
>
>
> Thanks,
>
> Durban
>
>
> This email and any files transmitted with it are confidential, proprietary
> and intended solely for the individual or entity to whom they are
> addressed. If you have received this email in error please delete it
> immediately.