Re: [Condor-users] RANK and job placement

[Dan Bradley <dan@xxxxxxxxxxxx>]

Hi Michael,

Here's a configuration that I have found to be useful in an environment 
similar to the one you describe:

NEGOTIATOR_PRE_JOB_RANK = 2 * (MY.RANK) + 1 * (RemoteOwner =?= UNDEFINED)

This will cause the negotiator to match the job preferentially to 
machines that favor it and secondarily to choose idle machines over 
occupied ones.

--Dan

Michael Thomas wrote:
> I have a condor pool with ~250 batch slots available.  On half of the
> batch slots I have set:
>
> RANK = (UserA =?= TRUE)
>
> ...and on the other half of the batch slots I have:
>
> RANK = (UserB =?= TRUE)
>
> This will allow both users to make use of free batch slots on the
> cluster, while guaranteeing that each user has access to 50% of the
> cluster resources.
>
> This has worked out pretty well for us so far.  But I've noticed some
> interesting behavior that I was hoping someone could help me tune.
> Occasionally I notice that UserA has ~20 jobs running, with the rest of
> the batch slots empty.  These 20 jobs are scattered across slots where
> the user has RANK priority and slots where the user does not have RANK
> priority.  Next, UserB comes along and submits a bazillion jobs.  This
> causes some of UserA's jobs to get evicted and restarted because some of
> UserA's jobs are running on batch slots where UserB has rank priority.
>
> When UserA submitted his 20 jobs, why were they not directed to batch
> slots where UserA had rank priority?  How can I get UserA's jobs to
> prefer those batch slots while still allowing him opportunistic access
> to the rest of the cluster?
>
> --Mike
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at: 
> https://lists.cs.wisc.edu/archive/condor-users/
>