SJSTAT(1)
πΈ sjstat(1) β the SLURM job-stats glow-up π
okay bestie, so sjstat lives in the User Contributed Perl Documentation section of the manual (section 1, for the record β¨), and honestly? it's giving "let me peek at what's actually happening on this cluster" energy and I am obsessed.
β¨ NAME β¨
sjstat β literally just: list attributes of jobs under the SLURM control. that's the whole vibe. π
π¦ SYNOPSIS π¦
sjstat [-h ] [-c] [-r ] [-v]
yes that's the exact spacing from the original, don't come for me π
π DESCRIPTION π
so the sjstat command is your new main character for displaying statistics of jobs under control of SLURM. the output is designed to give you the tea on resource usage and availablilty (yes, that's how it's spelled in the original, keeping it fr fr π«Ά), plus all the info about jobs that are currently active on the machine.
this output is built using the SLURM utilities sinfo, squeue and scontrol β and no cap, the man pages for those utilities will give you more information and greater depth of understanding. like, go read them. iykyk. π
π OPTIONS π
-hβ display a brief help message. tiny lil rescue when you're lost π«-cβ display the computing resource information only. just the resources, no job gossip π-manβ show the man page. iconic self-reference behavior, honestly π-rβ display only the running jobs. skip the pending girlies π-vβ display more verbose information. more fields, more lore, more everything π₯
β EXAMPLE β
the following is a basic request for status. slay, let's look:
> sjstat
Scheduling pool data:
------------------------------------------------------------
Pool Memory Cpus Total Usable Free Other Traits
------------------------------------------------------------
pdebug 15000Mb 8 32 32 24 (null)
pbatch* 15000Mb 8 1072 1070 174 (null)
Running job data:
-------------------------------------------------------------------
JobID User Nodes Pool Status Used Master/Other
-------------------------------------------------------------------
395 mary 1000 pbatch PD 0:00 (JobHeld)
396 mary 1000 pbatch PD 0:00 (JobHeld)
375 sam 1000 pbatch CG 0:00 (JobHeld)
388 fred 32 pbatch R 25:27 atlas89
361 harry 512 pbatch R 1:01:12 atlas618
1077742 sally 8 pdebug R 20:16 atlas18
π§ the scheduling data, explained
the scheduling data contains information pertaining to the:
- Pool β a set of nodes
- Memory β the amount of memory on each node
- Cpus β the number of cpus on each node
- Total β the total number of nodes in the pool
- Usable β total usaable nodes in the pool (their spelling, not mine, i promise π)
- Free β total nodes that are currently free
π the running job data, explained
the running job data contains information pertaining to the:
- JobID β the SLURM job id
- User β owner of the job
- Nodes β nodes required, or in use by the job (Note: on cpu scheduled machines, this field will be labeled "Procs" show the number of processors the job is using.)
- Pool β the Pool required or in use by the job
- Status β current status of the job
- Used β Wallclick time used by the job (again β exactly as written in the original π)
- Master/Other β either the Master (head) node used by the job, or may indicate further status of a pending, or completing job.
π the common status values
Rβ the job is running πPDβ the job is Pending β³CGβ the job is Completing π¬
these are states reported by SLURM and more elaborate documentation can be found in the squeue/sinfo man pages. go get that deep lore, bestie π«Ά
β¨ an example of the -v option β¨
Scheduling pool data:
-----------------------------------------------------------------------------
Total Usable Free Node Time Other
Pool Memory Cpus Nodes Nodes Nodes Limit Limit Traits
-----------------------------------------------------------------------------
pdebug 15000Mb 8 32 32 24 16 30 (null)
pbatch* 15000Mb 8 1072 1070 174 UNLIM UNLIM (null)
Running job data:
---------------------------------------------------------------------------------------------------
Time Time Time
JobID User Nodes Pool Status Used Limit Started Master/Other
---------------------------------------------------------------------------------------------------
38562 tom 4 pbatch PD 0:00 1:00:00 01-14T18:11:22 (JobHeld)
πΈ the added fields to the "Scheduling pool data"
- Node Limit β SLURM imposed node limit.
- Time Limit β SLURM imposed time limit, value in minutes.
πΈ the added fields to the "Running job data"
- Limit β time limit of job.
- Start β start time of job.
π REPORTING BUGS π
found a bug? report bugs to <eckert2@llnl.gov> β be nice, be specific, include the deets π
bestie reminder: the man pages forsinfo,squeueandscontrolare your besties too.sjstatis literally built from them, so that's where the full picture lives π
that's the whole page, no cap. this edition of the manual was brought to you by perl v5.40.2, dated 2026-10-14 β mwah, go check your queue πβ¨π¦
π¦ where this page comes from
- epel 10: slurm-contribs 26.05.5-1.el10_3 Β· GPL-2.0-or-later AND BSD-2-Clause AND BSD-1-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms