[slurm-users] Slurm Constraints handling

[Vicker, Darby (JSC-EG311)]

Use “Weight” to have slurm assign the non-IO nodes first.  

NodeName=pax11[00-03] Weight=2 Feature=10g
NodeName=pax11[04-31] Weight=1 

See the Weight section in “man slurm.conf” but this is the key for you:

       All things being equal, jobs will be allocated the nodes 
with the lowest weight which satisfies their requirements.

-----Original Message-----
From: slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of Götz Waschk <goetz.waschk at gmail.com>
Reply-To: Slurm User Community List <slurm-users at lists.schedmd.com>
Date: Monday, December 11, 2017 at 8:37 AM
To: "slurm-users at lists.schedmd.com" <slurm-users at lists.schedmd.com>
Subject: [slurm-users] Slurm Constraints handling

Hi everyone,

I was wondering how slurm is handling constraints.

I have a setup  with 32 nodes, pax11[00-31]. The first four machines
are for I/O and have 10G network interfaces. I have marked them in the
slurm.conf node configuration with
Feature=10g



Now I'm running test jobs with -N 8 --constraint=10g*1 so in theory,
four of these jobs could run at the same time. Intead, only one is
running at a time, it is assigned to
pax11-[00-07]. Is there a way to convince the scheduler to assign the
nodes like this instead?
pax11-00,pax11-[04-10]
pax11-01,pax11-[11-17]
pax11-02,pax11-[18-24]
pax11-03,pax11-[25-31]

Regards, Götz