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

Re: [HTCondor-users] Various options to fill depth first

On 12/15/2020 10:18 AM, ervikrant06@xxxxxxxxx wrote:
Hello Experts,

Still from HTCondor documentation I didn't find the answer of this query. 

Thanks & Regards,
Vikrant Aggarwal

Hi Vikrant,

My suggestion re the best option to fill depth first  is to cut-n-paste the configuration example from the HOWTO recipe:


Hope the above helps,

On Wed, Sep 2, 2020 at 9:49 AM Vikrant Aggarwal <ervikrant06@xxxxxxxxx> wrote:
Hello Experts,

Any thoughts on it. 

Thanks & Regards,
Vikrant Aggarwal

On Tue, Aug 18, 2020 at 4:53 PM Vikrant Aggarwal <ervikrant06@xxxxxxxxx> wrote:
Hello Experts,

After going through the various discussions I do see many options available to fill the depth first:

1) NEGOTIATOR_PRE_JOB_RANK - apart from serving the depth first, it serves other purposes like giving preference to one set of nodes over another. 

2) NEGOTIATOR_DEPTH_FIRST - Option introduced in the latest version of condor. Works pretty well to pack the nodes according to depth first. Boolean value can't be an _expression_.

3) CLAIM_PARTITIONABLE_LEFTOVERS - Sched level splitting for partitionable slots.

4) CONSUMPTION policies - Negotiator level splitting for partitionable slots.

My queries:

- Which option is best for filling the depth first?
- Tried to use NEGOTIATOR_PRE_JOB_RANK to fill depth first with (- cpus) but that didn't help.

Thanks & Regards,
Vikrant Aggarwal

HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: