Difference between revisions of "SLURM Job States"
Jump to navigation
Jump to search
Moskalenko (talk | contribs) |
|||
| Line 5: | Line 5: | ||
* '''BadConstraints''': The job resource request or constraints cannot be satisfied. The resource request includes such parameters as nodes, ntask, cpus-per-task, gpus (or gres=gpu...), partition, feature, constraint. In some cases this state is temporary e.g. if a job requests a full node or a large enough portion of a node that the scheduler cannot find appropriate resources right away. | * '''BadConstraints''': The job resource request or constraints cannot be satisfied. The resource request includes such parameters as nodes, ntask, cpus-per-task, gpus (or gres=gpu...), partition, feature, constraint. In some cases this state is temporary e.g. if a job requests a full node or a large enough portion of a node that the scheduler cannot find appropriate resources right away. | ||
* '''(Resources)''': The job request is waiting for resources. This could be due to a large number of job requests in the queue, and the scheduler cannot provide the resources immediately. | * '''(Resources)''': The job request is waiting for resources. This could be due to a large number of job requests in the queue, and the scheduler cannot provide the resources immediately. | ||
| + | * '''QOSGrpCpuLimit''': All CPU cores available for the listed account within the respective QOS are in use. | ||
| + | * '''QOSGrpMemLimit''': All memory available for the listed account within the respective QOS as described in the previous section is in use. | ||
Revision as of 20:41, 7 February 2023
See the SLURM squeue documentation for the full list of job states/reason codes. Here we list the most frequently encountered job states on HiPerGator for quick reference.
- BadConstraints: The job resource request or constraints cannot be satisfied. The resource request includes such parameters as nodes, ntask, cpus-per-task, gpus (or gres=gpu...), partition, feature, constraint. In some cases this state is temporary e.g. if a job requests a full node or a large enough portion of a node that the scheduler cannot find appropriate resources right away.
- (Resources): The job request is waiting for resources. This could be due to a large number of job requests in the queue, and the scheduler cannot provide the resources immediately.
- QOSGrpCpuLimit: All CPU cores available for the listed account within the respective QOS are in use.
- QOSGrpMemLimit: All memory available for the listed account within the respective QOS as described in the previous section is in use.