[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] scheduling behavior
- Date: Wed, 02 May 2018 14:55:10 -0700 (PDT)
- From: Marcus Ebert <mebert@xxxxxxx>
- Subject: Re: [HTCondor-users] scheduling behavior
On Wed, 2 May 2018, Todd Tannenbaum wrote:
On 5/2/2018 3:53 PM, Marcus Ebert wrote:
We have a condor 8.6 installation with about 4000 jobs slots. Most of
these are on 8-core VMs. When there are free slots available, the
scheduling of idle jobs to a specific machine seems somehow random.
What we would like to have is that HTCondor fills up all slots on a
machine before sending jobs to another (empty) machine.
Is there any config option that would allow to change the scheduling
behavior in that way (something like a node allocation policy in Maui)?
Are you using static slots (the default) or partitionable slots on your pool?
If you are using static slots, the default configuration should already prefer filling up a machine before using another machine.
If you are using partitionable slots, and you are running HTCondor v8.6.x or later, I suggest you append the following into the condor_config[.local] on your central manager and then do a condor_reconfig:
# If using partitionable slots, fill depth first. See http://tinyurl.com/y75k3k7p
NEGOTIATOR_DEPTH_FIRST = True
Yes, we are using partitionable slots (1 partitionable slot per VM).
I'll try that setting and let you know how it works.