squeue

The ‘squeue’ command will show users the jobs that are currently scheduled:

[johnchris@l001 ~]$ squeue

JOBIDJob or step ID
PARTITIONName of a partition. shared, exclusive, gpu100 and gpuv100 etc.
NAMEName of the job in the queue
USEROwner of the job in the queue
STState of the job. Include: allocated, completing, down, drained, draining, fail, failing, future, idle
TIMETime used by the job. days-hours:minutes
NODESNumber of nodes allocated to the job
NODELIST (REASON)For pending and failed jobs, this field displays the reason for pending or failure. Otherwise, this field shows a list of allocated nodes

The squeue command gives us the following information:

  • JOBID: The unique ID for your job.
  • PARTITION: The partition your job is running on (or scheduled to run on).
  • NAME: The name of your job.
  • USER: The username for whomever submitted the job.
  • ST: The status of the job. The typical status codes you may see are:
    • CD (Completed): Job completed successfully.
    • CG (Completing): Job is finishing, Slurm is cleaning up.
    • PD (Pending): Job is scheduled, but the requested resources aren’t available yet.
    • R (Running): Job is actively running.
  • TIME: How long your job has been running.
  • NODES: How many nodes your job is using.
  • NODELIST(REASON): Which nodes your job is running on (or scheduled to run on). If your job is not running yet, you will also see one of the following reason codes:
    • Priority: When Slurm schedules a job, it takes into consideration how frequently you submit jobs. If you often submit many jobs, Slurm will assign you a lower priority than someone who has never submitted a job or submits jobs very infrequently. Don’t worry, your job will run eventually.
    • Resources: Slurm is waiting for the requested resources to be available before starting your job.
    • Dependency: If you are using dependent jobs, the parent job may show this reason if it’s waiting for a dependent job to complete.

“squeue -u username” will view only the jobs from a specific user [johnchris@l001 ~]$ squeue -u johnchris

[johnchris@l001 ~]$ squeue -u johnchris --start

Note: The job start time is an estimate; it may change as other jobs are submitted. The memory and wall clock time parameters require you to estimate the amount of time your job will need to finish. If you underestimate, your job may be killed before it completes. If you overestimate, your job may take longer to start, as the queuing system finds a way to allocate the resources.

Scroll to Top