[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] prioritizing one group of machines over another
- Date: Wed, 20 Jan 2016 11:50:55 -0500
- From: Michael V Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>
- Subject: Re: [HTCondor-users] prioritizing one group of machines over another
From: Thomas Hartmann <thomas.hartmann@xxxxxxxx>
Date: 01/20/2016 05:35 AM
> i have two groups of machines in my setup. the machines of one group
> faster, more reliable. is it possible to tell the scheduler to only
> submit jobs to the other group if the first group of machines cannot
> take any more jobs?
What you're looking for is the RANK _expression_:
The manual gives the example of memory size of the
jobs as a determining
factor, but in your case you'd want to use, for example,
KFlops attribute, so that the faster machines get
top priority for jobs.
Similarly, I have a startd_cron which probes the network
and incorporates that into the rank _expression_, so
that machines with
bonded or 10G interfaces get preference over single-interface
If you're using partitionable slots this can go a
bit sideways depending
on how you're configured - by default the negotiator
will make a trip
through all of the partitionable slots, which means
that it will include
the low-ranked machines' partitionable slots in its
matching and you'll
wind up with one job on each machine in both groups.
If I'm remembering
correctly, using consumption policies instead of claim
leftovers addresses this.