Difference between revisions of "Why is my job not running"

From UFRC
Jump to navigation Jump to search
Line 1: Line 1:
 
[[Category:Scheduler]]
 
[[Category:Scheduler]]
According to SLURM documentation as soon as a reason is found why a job cannot be started that reason is recorded in the job's "reason" field in the squeue output and the scheduler moves on to the next job to consider.
+
According to SLURM documentation, when a job cannot be started a reason is immediately found and recorded in the job's "reason" field in the squeue output and the scheduler moves on to the next job to consider.
  
 
Common reasons why jobs are pending:
 
Common reasons why jobs are pending:

Revision as of 14:13, 20 April 2022

According to SLURM documentation, when a job cannot be started a reason is immediately found and recorded in the job's "reason" field in the squeue output and the scheduler moves on to the next job to consider.

Common reasons why jobs are pending:

Priority
Resources being reserved for higher priority job. This is particularly common on Burst QOS jobs. Refer to the Choosing QOS for a Job page for details.
Resources
Required resources are in use
Dependency
Job dependencies not yet satisfied
Reservation
Waiting for advanced reservation
AssociationJobLimit
User or account job limit reached
AssociationResourceLimit
User or account resource limit reached
AssociationTimeLimit
User or account time limit reached
QOSJobLimit
Quality Of Service (QOS) job limit reached
QOSResourceLimit
Quality Of Service (QOS) resource limit reached
QOSTimeLimit
Quality Of Service (QOS) time limit reached