Familiarity with Slurm's Accounting web page is strongly recommended before use of this document.
Slurm's hierarchical limits are enforced in the following order with Job QOS and Partition QOS order being reversible by using the QOS flag 'OverPartQOS':
- Partition QOS limit
- Job QOS limit
- User association
- Account association(s), ascending the hierarchy
- Root/Cluster association
- Partition limit
Note: If limits are defined at multiple points in this hierarchy, the point in this list where the limit is first defined will be used. Consider the following example:
- MaxJobs=20 and MaxSubmitJobs is undefined in the partition QOS
- No limits are set in the job QOS and
- MaxJobs=4 and MaxSubmitJobs=50 in the user association
The limits in effect will be MaxJobs=20 and MaxSubmitJobs=50.
Note: The precedence order specified above is respected except for the following limits: Max[Time|Wall], [Min|Max]Nodes. For these limits, even if the job is enforced with QOS and/or Association limits, it can't go over the limit imposed at Partition level, even if it listed at the bottom. So the default for these 3 types of limits is that they are upper bound by the Partition one. This Partition level bound can be ignored if the respective QOS PartitionTimeLimit and/or Partition[Max|Min]Nodes flags are set, then the job would be enforced the limits imposed at QOS and/or association level respecting the order above.
Scheduling policy information must be stored in a database as specified by the AccountingStorageType configuration parameter in the slurm.conf configuration file. Information can be recorded in a MySQL or MariaDB database. For security and performance reasons, the use of SlurmDBD (Slurm Database Daemon) as a front-end to the database is strongly recommended. SlurmDBD uses a Slurm authentication plugin (e.g. MUNGE). SlurmDBD also uses an existing Slurm accounting storage plugin to maximize code reuse. SlurmDBD uses data caching and prioritization of pending requests in order to optimize performance. While SlurmDBD relies upon existing Slurm plugins for authentication and database use, the other Slurm commands and daemons are not required on the host where SlurmDBD is installed. Only the slurmdbd and slurm-plugins RPMs are required for SlurmDBD execution.
Both accounting and scheduling policies are configured based upon an association. An association is a 4-tuple consisting of the cluster name, bank account, user and (optionally) the Slurm partition. In order to enforce scheduling policy, set the value of AccountingStorageEnforce. This option contains a comma separated list of options you may want to enforce. The valid options are:
- associations - This will prevent users from running jobs if their association is not in the database. This option will prevent users from accessing invalid accounts.
- limits - This will enforce limits set to associations. By setting this option, the 'associations' option is also set.
- qos - This will require all jobs to specify (either overtly or by default) a valid qos (Quality of Service). QOS values are defined for each association in the database. By setting this option, the 'associations' option is also set.
- safe - This will ensure a job will only be launched when using an association or qos that has a GrpCPUMins limit set if the job will be able to run to completion. Without this option set, jobs will be launched as long as their usage hasn't reached the cpu-minutes limit which can lead to jobs being launched but then killed when the limit is reached. By setting this option, both the 'associations' option and the 'limits' option are set automatically.
- wckeys - This will prevent users from running jobs under a wckey that they don't have access to. By using this option, the 'associations' option is also set. The 'TrackWCKey' option is also set to true.
(NOTE: The association is a combination of cluster, account,
user names and optional partition name.)
Without AccountingStorageEnforce being set (the default behavior) jobs will be executed based upon policies configured in Slurm on each cluster.
The tool used to manage accounting policy is sacctmgr. It can be used to create and delete cluster, user, bank account, and partition records plus their combined association record. See man sacctmgr for details on this tools and examples of its use.
Changes made to the scheduling policy are uploaded to the Slurm control daemons on the various clusters and take effect immediately. When an association is deleted, all running or pending jobs which belong to that association are immediately canceled. When limits are lowered, running jobs will not be canceled to satisfy the new limits, but the new lower limits will be enforced.
Limits in both Associations and QOS
When dealing with Associations, most of these limits are available not only for a user association, but also for each cluster and account. If a new association is created for some user and a scheduling policy option is not specified the default will be: the option for the cluster/account pair, and if both are not specified then the option for the cluster, and if that also is not specified then no limit will apply.
NOTE: Unless noted, if a job request breaches a given limit the job will pend unless the job's QOS has the DenyOnLimit flag set, which will cause the job to be denied at submission. When Grp limits are considered with respects to this flag the Grp limit is treated as a Max limit.
NOTE: When modifying a TRES field with sacctmgr, one must specify which TRES's to modify (see TRES for complete list) as in the following examples:
SET: sacctmgr modify user bob set GrpTRES=cpu=1500,mem=200,gres/gpu=50 UNSET: sacctmgr modify user bob set GrpTRES=cpu=-1,mem=-1,gres/gpu=-1
- GrpTRESMins= The total number of TRES minutes that can possibly be used by past, present and future jobs running from an association and its children or QOS. If this limit is reached all jobs running in this group will be killed, and no new jobs will be allowed to run. This usage is decayed (at a rate of PriorityDecayHalfLife). It can also be reset (according to PriorityUsageResetPeriod) in order to allow jobs to run against the association tree or QOS again. QOS that have the NoDecay flag set do not decay GrpTRESMins, see QOS Options for details. This limit only applies when using the Priority Multifactor plugin.
- GrpTRESRunMins= Used to limit the combined total number of TRES minutes used by all jobs running with an association and its children or QOS. This takes into consideration time limit of running jobs and consumes it, if the limit is reached no new jobs are started until other jobs finish to allow time to free up.
- GrpTRES= The total count of TRES able to be used at any given time from jobs running from an association and its children or QOS. If this limit is reached new jobs will be queued but only allowed to run after resources have been relinquished from this group.
- GrpJobs= The total number of jobs able to run at any given time from an association and its children QOS. If this limit is reached new jobs will be queued but only allowed to run after previous jobs complete from this group.
- GrpJobsAccrue= The total number of pending jobs able to accrue age priority at any given time from an association and its children QOS. If this limit is reached new jobs will be queued but not accrue age priority until after previous jobs are removed from pending in this group. This limit does not determine if the job can run or not, it only limits the age factor of the priority.
- GrpSubmitJobs= The total number of jobs able to be submitted to the system at any given time from an association and its children or QOS. If this limit is reached new submission requests will be denied until previous jobs complete from this group.
- GrpWall= The maximum wall clock time any job submitted to this group can run for. If this limit is reached submission requests will be denied. This usage is decayed (at a rate of PriorityDecayHalfLife). It can also be reset (according to PriorityUsageResetPeriod) in order to allow jobs to run against the association tree or QOS again. QOS that have the NoDecay flag set do not decay GrpWall, see QOS Options for details.
- MaxTRESMinsPerJob= A limit of TRES minutes to be used by a job. If this limit is reached the job will be killed if not running in Safe mode, otherwise the job will pend until enough time is given to complete the job.
- MaxTRESPerJob= The maximum size in TRES any given job can have from the association/QOS.
- MaxTRESPerNode= The maximum size in TRES each node in a job allocation can use.
- MaxWallDurationPerJob= The maximum wall clock time any job submitted can run for the given association/QOS. If this limit is reached the job will be denied at submission.
- MinPrioThreshold= Used to override bf_min_prio_reserve, see bf_min_prio_reserve for details.
Association specific scheduling policies supported
These represent the scheduling policies unique to associations. Shared policies and limits QOS has in common are listed later.
- Fairshare= Integer value used for determining priority. Essentially this is the amount of claim this association and it's children have to the above system. Can also be the string "parent", when used on a user this means that the parent association is used for fairshare. If Fairshare=parent is set on an account, that account's children will be effectively re-parented for fairshare calculations to the first parent of their parent that is not Fairshare=parent. Limits remain the same, only it's fairshare value is affected.
- MaxJobs= The total number of jobs able to run at any given time for the given association. If this limit is reached new jobs will be queued but only allowed to run after previous jobs complete from the association.
- MaxJobsAccrue= The maximum number of pending jobs able to accrue age priority at any given time for the given association. If this limit is reached new jobs will be queued but not accrue age priority until after previous jobs are removed from pending using this association. This limit does not determine if the job can run or not, it only limits the age factor of the priority.
- MaxSubmitJobs= The maximum number of jobs able to be submitted to the system at any given time from the given association. If this limit is reached new submission requests will be denied until previous jobs complete from this association.
- QOS= comma separated list of QOS's an association is able to run.
QOS specific limits supported
- MaxJobsAccruePerAccount= The maximum number of pending jobs an account (or subacct) can have accruing age priority at any given time. This limit does not determine if the job can run or not, it only limits the age factor of the priority.
- MaxJobsAccruePerUser= The maximum number of pending jobs a user can have accruing age priority at any given time. This limit does not determine if the job can run or not, it only limits the age factor of the priority.
- MaxJobsPerAccount= The maximum number of jobs an account (or subaccount) can have running at a given time.
- MaxJobsPerUser= The maximum number of jobs a user can have running at a given time.
- MaxSubmitJobsPerAccount= The maximum number of jobs an account (or subaccount) can have running and pending at a given time.
- MaxSubmitJobsPerUser= The maximum number of jobs a user can have running and pending at a given time.
- MaxTRESPerAccount= The maximum number of TRES an account can allocate at a given time.
- MaxTRESPerUser= The maximum number of TRES a user can allocate at a given time.
- MinTRESPerJob= The minimum size in TRES any given job can have when using the requested QOS.
The MaxNodes and MaxWall options already exist in Slurm's configuration on a per-partition basis, but the above options provide the ability to impose limits on a per-user basis. The MaxJobs option provides an entirely new mechanism for Slurm to control the workload any individual may place on a cluster in order to achieve some balance between users.
Fair-share scheduling is based upon the hierarchical bank account data maintained in the Slurm database. More information can be found in the priority/multifactor plugin description.
Specific limits over GRES
When a GRES has a type associated with it and a limit is applied over this specific type, i.e. MaxTRESPerUser=gres/gpu:tesla=1, if a user requests a generic gres, the type's limit will not be enforced. In this situation an additional lua job submit plugin to check the user request may become useful. For example, if one requests --gres=gpu:2 having a limit set of MaxTRESPerUser=gres/gpu:tesla=1, the limit won't be enforced so it will still be possible to get two teslas.
This is due to a design limitation. The only way to enforce such a limit is to combine the specification of the limit with a job submit plugin that forces the user to always request a specific type model.
An example of basic lua job submit plugin function could be:
function slurm_job_submit(job_desc, part_list, submit_uid) if (job_desc.gres ~= nil) then for g in job_desc.gres:gmatch("[^,]+") do bad = string.match(g,'^gpu[:]*[0-9]*$') if (bad ~= nil) then slurm.log_info("User specified gpu GRES without type: %s", bad) slurm.user_msg("You must always specify a type when requesting gpu GRES") return slurm.ERROR end end end end
Having this script and the limit in place will force the users to always specify a gpu with its type, thus enforcing the limits for each specific model.
It is also advisable to set AccountingStorageTRES for both generic and specific gres types, otherwise requests that ask for generic only gpus won't be accounted for. Set this for example to:
See Trackable Resources TRES for details.
Last modified 1 May 2018