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

Re: [HTCondor-users] execute host priority



I would not have thought giving one execute host priority over another
would be that difficult. But I have googled this and I see it's been
asked quite a few times, with no clear answer ever given.

On Wed, Feb 7, 2018 at 12:26 PM, Larry Martell <larry.martell@xxxxxxxxx> wrote:
> How do I use this setting? From googling I tried this on the machine I
> want to have lower priority:
>
> NEGOTIATOR_PRE_JOB_RANK = - Memory
>
> But it had no effect - that machine was still chosen first.
>
> On Thu, Jan 18, 2018 at 5:59 PM, John M Knoeller <johnkn@xxxxxxxxxxx> wrote:
>> Use NEGOTIATOR_PRE_JOB_RANK if you want to choose which machine is given to
>> the schedd first.
>>
>>
>>
>> From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf
>> Of Larry Martell
>> Sent: Thursday, January 18, 2018 4:21 PM
>> To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
>> Subject: Re: [HTCondor-users] execute host priority
>>
>>
>>
>> Do it put that in just one host (the one I want it to use first)?
>>
>>
>>
>> On Thu, Jan 18, 2018 at 5:09 PM John M Knoeller <johnkn@xxxxxxxxxxx> wrote:
>>
>> This will happen naturally if your execute nodes are configured to use
>> partitionable slots. with CLAIM_PARTITIONABLE_LEFTOVERS=true in the schedd.
>>
>> The schedd will get handed the entire partitionable slot, and it will split
>> it up and start as many jobs on it as it can before it will try to cuse the
>> other partitionable slot.
>>
>> If there are more than 136 jobs in the queue, then the second execute
>> machine will end up getting used for the remaining jobs.
>>
>> -tj
>>
>> -----Original Message-----
>> From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf
>> Of Larry Martell
>> Sent: Thursday, January 18, 2018 6:14 AM
>> To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
>> Subject: [HTCondor-users] execute host priority
>>
>> I have 2 execute hosts defined each with 136 cores - how can I make my
>> submit host use all the cores on one before starting to use the other?