Slurm Workload Manager: Difference between revisions

Revision as of 08:53, 28 November 2019

Latest revision as of 15:59, 22 July 2025

(37 intermediate revisions by 31 users not shown)

Line 1:

{{short description|Free and open-source job scheduler for Linux and similar computers}}

{{Multiple issues|

{{primary sources|date=July 2010}}

{{Notability|date=July 2010}}

}}

{{Infobox software

| title = Slurm

Line 8 ⟶ 6:

| logo = Slurm logo.svg

| logo caption =

| developer = [[SchedMD]]

| screenshot = <!-- Image name is enough -->

| caption =

Line 14 ⟶ 13:

| released = <!-- {{Start date and age|YYYY|MM|DD|df=yes/no}} -->

| discontinued =

| latest release version = 19.05.5, 18.08.8{{wikidata|property|preferred|references|edit@end|P348|P548=Q2804309}}

| latest release date = <!-- {{Startstart date and age|YYYY{{wikidata|MMqualifier|DDP348|P548=Q2804309|P577}}|df=yes/no}} -->

| programming language = [[C (programming language)|C]]

| operating system = [[Linux]], [[BSD]]s

| platform =

| size =

| genre = Job Scheduler for Clusters and Supercomputers

| license = [[GNU General Public License]]

| website = {{Official URL|https://slurm.schedmd.com/}}

| logo_size = 170px

| logo_alt =

Line 29 ⟶ 28:

}}

The '''Slurm Workload Manager''', (formerly known as '''Simple Linux Utility for Resource Management''' or ('''SLURM'''), or simply '''Slurm''', is a [[free and open-source]] [[job scheduler]] for [[Linux]] and [[Unix-like]] [[Kernelkernel (operating system)|kernels]], used by many of the world's [[supercomputer]]s and [[computer cluster]]s.

It provides three key functions:

* allocating exclusive and/or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work,

* providing a framework for starting, executing, and monitoring work, (typically a parallel job such as [[Message Passing Interface|MPI]] (MPI) on a set of allocated nodes, and

* arbitrating contention for resources by managing a queue of pending jobs.

Slurm is the workload manager on about 60% of the [[TOP500]] supercomputers.<ref>{{Cite web|url=https://hpcc.usc.edu/support/documentation/slurm/|title=Running a Job on HPC using Slurm {{!}} HPC {{!}} USC|website=hpcc.usc.edu|access-date=2019-03-05|archive-date=2019-03-06|archive-url=https://web.archive.org/web/20190306044130/https://hpcc.usc.edu/support/documentation/slurm/|url-status=dead}}</ref>

Slurm uses a [[curve fittingBest-fit_bin_packing|best fit algorithm]] based on [[Hilbert curve scheduling]] or [[fat tree]] network topology in order to optimize locality of task assignments on parallel computers.<ref name=Eitan>{{Cite conference|doi=10.1007/978-3-642-04633-9_8|title=Effects of Topology-Aware Allocation Policies on Scheduling Performance|conference=Job Scheduling Strategies for Parallel Processing|series=Lecture Notes in Computer Science|year=2009|last1=Pascual|first1=Jose Antonio|last2=Navaridas|first2=Javier|last3=Miguel-Alonso|first3=Jose|isbn=978-3-642-04632-2|volume=5798|pages=138–144}}</ref>

==History==

Slurm began development as a collaborative effort primarily by [[Lawrence Livermore National Laboratory]], [[SchedMD]],<ref>{{cite web|url=https://www.schedmd.com/ |title=Slurm Commercial Support, Development, and Installation |publisher=SchedMD |access-date= |accessdate=2014-02-23}}</ref> Linux NetworX, [[Hewlett-Packard]], and [[Groupe Bull]] as a Free Software resource manager. It was inspired by the closed source [[QuadricsRmsQuadrics_(company)| Quadrics RMS]] and shares a similar syntax. The name is a reference to the [[Fry and the Slurm Factory#Slurm|soda]] in [[Futurama]].<ref>{{cite web|url=https://slurm.schedmd.com/slurm_design.pdf |title=SLURM: Simple Linux Utility for Resource Management |date=23 June 2003 |accessdateaccess-date=11 January 2016}}</ref> Over 100 people around the world have contributed to the project. It has since evolved into a sophisticated batch scheduler capable of satisfying the requirements of many large computer centers.

{{As of|20172021|November}}, [[TOP500]] list of most powerful computers in the world indicates that Slurm is the workload manager on sixmore than half of the top ten systems including the [[Sunway TaihuLight]] with 10,649,600 computing cores.

==Structure==

Slurm's design is very modular with about 100 optional plugins. In its simplest configuration, it can be installed and configured in a couple of minutes. More sophisticated configurations provide database integration for accounting, management of resource limits and workload prioritization.

==Features==

==Notable features==

Notable Slurm features include the following:{{Citation needed|date=September 2014}}

* No single point of failure, backup daemons, fault-tolerant job options

Line 73 ⟶ 72:

* Support for MapReduce+

* Support for [[burst buffer]] that accelerates scientific data movement

The following features are announced for version 14.11 of Slurm, was released in November 2014:<ref>{{cite web|url=https://slurm.schedmd.com/news.html |title=Slurm - What's New |publisher=SchedMD |date= |accessdate=2014-08-29}}</ref>

* Improved job array data structure and scalability

* Support for heterogeneous generic resources

* Add user options to set the CPU governor

* Automatic job requeue policy based on exit value

* Report API use by user, type, count and time consumed

* Communication gateway nodes improve scalability

==Supported platforms==

Recent Slurm isreleases primarilyrun developedonly to work alongsideon [[Linux]]. distributions, althoughOlder thereversions ishad alsobeen supportported forto a few other [[POSIX]]-based [[operating system]]s, including [[BSD]]s ([[FreeBSD]], [[NetBSD]] and [[OpenBSD]]).,<ref>[https://slurm.schedmd.com/platforms.html Slurm Platforms]</ref> but Slurmthis alsois supportsno several unique computer architectures, including:longer

feasible as Slurm now requires [[cgroups]] for core operations. Clusters running operating systems other than Linux will need to use

a different batch system, such as LPJS. Slurm also supports several unique computer architectures, including:

* [[IBM]] [[BlueGene]]/Q models, including the 20 petaflop [[IBM Sequoia]]

* [[Cray]] XT, XE and Cascade

* [[Tianhe-2]] a 33.9 petaflop system with 32,000 Intel Ivy Bridge chips and 48,000 Intel Xeon Phi chips with a total of 3.1 million cores

* [http://www-03.ibm.com/systems/software/parallel IBM Parallel Environment]

* [[Anton (computer)|Anton]]

==License==

Slurm is available under the [[GNU General Public License#History|GNU General Public License v2]] V2.

==Commercial support==

In 2010, the developers of Slurm founded ''SchedMD'', which maintains the canonical source, provides development, level 3 commercial support and training services. Commercial support is also available from [[BrightGroupe ComputingBull|Bull]], ''Bull'', ''[[Cray'']], and ''Science + Computing'' (subsidiary of [[Atos]]).

== Usage ==

[[File:EstadosTrabajosSLURM.jpg|thumb|Slurm distinguishes several stages for a job]]

The <code>slurm</code> system has three main parts:

* <code>slurmctld</code>, a central control [[Daemon (computing)|daemon]] running on a single control node (optionally with [[failover]] backups);

* many computing nodes, each with one or more <code>slurmd</code> daemons;

* clients that connect to the manager node, often with [[Secure Shell|ssh]].

The clients can issue commands to the control daemon, which would accept and divide the workload to the computing daemons.

For clients, the main commands are <code>srun</code> (queue up an interactive job), <code>sbatch</code> (queue up a job), <code>squeue</code> (print the job queue) and <code>scancel</code> (remove a job from the queue).

Jobs can be run in [[Batch processing|batch mode]] or [[Interactive computing|interactive mode]]. For interactive mode, a compute node would start a shell, connects the client into it, and run the job. From there the user may observe and interact with the job while it is running. Usually, interactive jobs are used for initial debugging, and after debugging, the same job would be submitted by <code>sbatch</code>. For a batch mode job, its <code>stdout</code> and <code>stderr</code> outputs are typically directed to text files for later inspection.

==See also==

Line 106 ⟶ 114:

* [[TORQUE]]

* [[Univa Grid Engine]]

* [[Platform LSF]]

==References==

Line 114 ⟶ 123:

* {{Cite conference|doi=10.1007/978-3-540-78699-3_3|title=Enhancing an Open Source Resource Manager with Multi-core/Multi-threaded Support|conference=Job Scheduling Strategies for Parallel Processing|series=[[Lecture Notes in Computer Science]]|year=2008|last1=Balle|first1=Susanne M.|last2=Palermo|first2=Daniel J.|isbn=978-3-540-78698-6|volume=4942|page=37}}

* {{Cite journal|last1=Jette|first1= M. |first2= M. |last2=Grondona|url=https://slurm.schedmd.com/slurm_design.pdf |title=SLURM: Simple Linux Utility for Resource Management|journal=Proceedings of ClusterWorld Conference and Expo|___location=San Jose, California|date=June 2003}}

* {{cite journal|last=Layton|first= Jeffrey B. |url=http://www.linux-mag.com/id/7239/1/|archive-url=https://web.archive.org/web/20090211041650/http://www.linux-mag.com/id/7239/1/|url-status=usurped|archive-date=February 11, 2009|title= Caos NSA and Perceus: All-in-one Cluster Software Stack|journal= Linux Magazine|date=5 February 2009}}

* {{cite conference|doi=10.1007/10968987_3|title=SLURM: Simple Linux Utility for Resource Management|conference=Job Scheduling Strategies for Parallel Processing|series=Lecture Notes in Computer Science|year=2003|last1=Yoo|first1=Andy B.|last2=Jette|first2=Morris A.|last3=Grondona|first3=Mark|isbn=978-3-540-20405-3|volume=2862|page=[https://archive.org/details/jobschedulingstr0000jssp_q2o1/page/44 44]|citeseerx=10.1.1.10.6834|url-access=registration|url=https://archive.org/details/jobschedulingstr0000jssp_q2o1/page/44}}

{{Div col end}}

==Slurm Commands==

The following is a list of useful commands available for Slurm. Some of these were built by CCR to allow easier reporting for users.

For usage information for these commands, use {{code|--help}} (example: {{code|sinfo --help}}).

Use the Linux command {{code|man}} for more information about most of these commands (example: {{code|man sinfo}}).

Italicized font on the commands below indicates user supplied information. Brackets indicate optional flags.

{| class="wikitable"

|-

! List Slurm commands !! slurmhelp

|-

| View information about Slurm nodes & partitions || sinfo ''[-p partition_name or -M cluster_name]''

|-

| List example Slurm scripts || ls -p /util/slurm-scripts less

|-

| Submit a job script for later execution || sbatch ''script-file''

|-

| Cancel a pending or running job || scancel ''jobid''

|-

| Check the state of a user's jobs || squeue—user=''username''

|-

| Allocate compute nodes for interactive use || salloc

|-

| Run a command on allocated compute nodes || srun

|-

| Display node information || snodes ''[node cluster/partition state]''

|-

| Launch an interactive job || fisbatch ''[various sbatch options]''

|-

| List priorities of queued jobs ||sranks

|-

| Get the efficiency of a running job || sueff ''user-name''

|-

| Get Slurm accounting information for a user's jobs from start date to now || suacct start-date ''user-name''

|-

| Get Slurm accounting and node information for a job || slist ''jobid''

|-

| Get resource usage and accounting information for a user's jobs from start date to now || slogs ''start-date user-list''

|-

| Get estimated starting times for queued jobs || stimes ''[various squeue options]''

|-

| Monitor performance of a Slurm job || /util/ccrjobvis/slurmjobvis ''jobid''

|}

==External links==

* {{Official website}}

* [https://slurm.schedmd.com Slurm Documentation]

* [https://www.schedmd.com SchedMD]

* [https://www.open-mpi.org/video/slurm/Slurm_EMC_Dec2012.pdf Slurm Workload Manager Architecture Configuration and Use ]

* [https://s3-us-west-2.amazonaws.com/imss-hpc/index.html Caltech HPC Center: Job Script Generator]

{{Linux kernel}}

Line 176 ⟶ 140:

[[Category:Grid computing]]

[[Category:Cluster computing]]

[[Category:Free software programmed in C]]

[[Category:Software using the GNU General Public License]]