Slurm Workload Manager: Difference between revisions

Revision as of 20:10, 17 September 2024

Revision as of 20:55, 24 December 2024

Line 98:

== 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 `slurmctld` (slurm 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==