[slurm-users] Requirement to use QOS?

1,848 views
Skip to first unread message

Loris Bennett

unread,
Jan 19, 2018, 3:51:17 AM1/19/18
to Slurm Users Mailing List
Hi,

Some while ago I defined several QOS thus:

Name Priority MaxWall MaxJobs MaxSubmit
---------- ---------- ----------- ------- ---------
normal 0
short 100000 03:00:00 10 20
medium 10000 3-00:00:00 100 200
long 1000 14-00:00:00

This worked OK with Slurm 17.02.7 and previous versions. The default
QOS for all users was 'long' and all users were able to use both 'short'
and 'medium'.

Recently, still using version 17.02.7, I added a restriction on the
number of cores per user thus:

Name Priority MaxWall MaxJobs MaxSubmit MaxTRESPU
---------- ---------- ----------- ------- --------- -------------
normal 0
short 100000 03:00:00 10 20 cpu=20
medium 10000 3-00:00:00 100 200 cpu=200
long 1000 14-00:00:00

However, now users are unable to use 'short' and 'medium' as the
following error is produces by 'sbatch':

sbatch: error: Batch job submission failed: Invalid qos specification

Deleting the MaxTRESPerUser settings does not fix the problem.

My assumption is that that some change in this or a previous version was
made in the way QOS can be accessed by associations, but this change has
only now manifested itself after the QOS have been updated.

Can anyone confirm this?

Cheers,

Loris

--
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin Email loris....@fu-berlin.de

Loris Bennett

unread,
Jan 22, 2018, 4:03:16 AM1/22/18
to Slurm User Community List
In a similar vein, the documentation for 'sacctmgr' says

Note: the QOS that can be used at a given account in the hierarchy are
inherited by the children of that account.

However, if I do the following:

$ sacctmgr modify account name=root set qos+=medium,short

the result is

Modified account associations...
C = soroban A = root
C = soroban A = anemometry U = alice
C = soroban A = anemometry U = bob
C = soroban A = barometry U = carol
C = soroban A = barometry U = dave
C = soroban A = calorimetry U = ethel
...

To me this looks as if the QOS are in fact being explicitly added to
each association. In this case, will a new association added within
this hierarchy automatically be associated with the QOS available to the
other associations?

Loris Bennett

unread,
Jan 29, 2018, 3:13:22 AM1/29/18
to Slurm User Community List
Can anyone shed any light on this issue?
Reply all
Reply to author
Forward
0 new messages