Re: [HTCondor-users] gpu's and preemption

[Collin Mehring <collin.mehring@xxxxxxxxxxxxxx>]

Hi Michael,

The following should do what you're asking for.

In the startd configuration:

RANK = RequestGPUs

# Append this to the existing list if you already define this macro

STARTD_JOB_ATTRS =ÂRequestGPUs

In the negotiator configuration:

NEGOTIATOR_CONSIDER_PREEMPTION = True

ALLOW_PSLOT_PREEMPTION = True

PREEMPTION_REQUIREMENTS = Target.RequestGPUs > 0 && My.RequestGPUs =?= 0

Hope that helps,

Collin

On Thu, Feb 28, 2019 at 4:55 PM Michael Di Domenico <mdidomenico4@xxxxxxxxx> wrote:

On Thu, Feb 28, 2019 at 3:27 PM Todd L Miller <tlmiller@xxxxxxxxxxx> wrote:
> > ideally what i'd like to happen is that 4 of usera's jobs are
> > preempted for userb's. just the fact that a user is asking for a gpu
> > should be enough to preempt another person from a slot that isn't
>
>Â Â Â Â ÂThis sounds like a job for a (machine) RANK _expression_.
> (Something like RANK = RequestGPUs, probably.)Â That will work just fine
> with pslots, except ...

wait, so you're saying all i need to do is set preempt = true and rank
= requestgpus to get the desired behaviour. that doesn't sound right

the gist of what i'm trying to do is allow gpu jobs to push non-gpu
jobs off the slot and cut the line for the slot. all other jobs
should not preempt (this is where i got into trouble before). i had
huge swings in the pool as the prio's changed and jobs got preempted

given my last foray into pre-emption I'm unwilling to turn the knobs
until i know which specifically i need to turn
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

--

Collin Mehring | PE-JoSE - Software Engineer