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

Re: [HTCondor-users] priority for single jobs



START is more like a condition to start job on machine. AFAIK it's expected to see higher priority of START in-comparison to RANK.Â

Thanks & Regards,
Vikrant Aggarwal


On Thu, Aug 15, 2019 at 6:41 PM Carlos Adean <carlosadean@xxxxxxxxxxxx> wrote:
sHi Condor experts,


I have this configuration that prioritizes whole machine jobs, and it works well.

START = True
KILL = False
PREEMPT = False
RANK = None
SUSPEND = False
WANT_SUSPEND = False
WANT_VACATE = False
STARTD_EXPRS = $(STARTD_EXPRS)
UPDATE_COLLECTOR_WITH_TCP = True

START = ($(START)) && (TARGET.RequiresWholeMachine =!= TRUE || SlotID == 1)
STARTD_JOB_EXPRS = $(STARTD_JOB_EXPRS) RequiresWholeMachine
STARTD_SLOT_EXPRS = RequiresWholeMachine
START = ($(START)) && (SlotID == 1 || Slot1_RequiresWholeMachine =!= True)


However, I need to setup a node that should run any kind of job but giving
more priority for a single job, even if it means to kick out a whole machine job.

I tried to setup the htcondor to give more priority for specific users adding the configuration
below and replacing the value of RANK, but it does not seem to be suficient.


TnoUsers = (Owner == 'fulano') && (Owner == 'ciclano')
RANK = $(TnoUsers)*10

I noticed that the current START configuration has more weight than RANK, is this correct?


thanks,



--
C. Adean
_______________________________________________
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/