Difference between revisions of "SLURM/JobStatus"

From UMIACS
Jump to navigation Jump to search
(Created page with "=Job Status= SLURM offers a variety of tools to check the status of your jobs before, during, and after it has begun/completed. When you first submit your job, SLURM should gi...")
 
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
=Job Status=
 
=Job Status=
SLURM offers a variety of tools to check the status of your jobs before, during, and after it has begun/completed. When you first submit your job, SLURM should give you a job ID, this represents the resources allocated to your job, individual calls to srun will spawn job steps which can also be queried individually.
+
SLURM offers a variety of tools to check the status of your jobs before, during, and after execution. When you first submit your job, SLURM should give you a job ID which represents the resources allocated to your job. Individual calls to srun will spawn job steps which can also be queried individually.
  
 
==squeue==
 
==squeue==
The squeue command shows job status in the queue. If your job has not yet started you can ask for an estimated start time with <code>squeue --start</code>
+
The squeue command shows job status in the queue. Helpful flags:
 +
* <code>-u username</code> to show only your jobs (replace username with your UMIACS username)
 +
* <code>--start</code> to estimate start time for a job that has not yet started and the reason why it is waiting
 +
* <code>-s</code> to show the status of individual job steps for a job (e.g. batch jobs)
 +
 
 +
Examples:
 
<pre>
 
<pre>
tgray26@shadosub:squeue
+
username@nexusclip00:squeue -u username
 
             JOBID PARTITION    NAME    USER ST      TIME  NODES NODELIST(REASON)
 
             JOBID PARTITION    NAME    USER ST      TIME  NODES NODELIST(REASON)
               162    test2 helloWor tgray26 R      0:03      2 shado[00-01]
+
               162    test2 helloWor username R      0:03      2 tron[00-01]
 +
</pre>
 +
 
 +
<pre>
 +
username@nexusclip00:squeue --start -u username
 +
            JOBID PARTITION    NAME    USER ST          START_TIME  NODES SCHEDNODES          NODELIST(REASON)
 +
              163    test2 helloWo2 username PD 2020-05-11T18:36:49      1 tron02            (Priority)
 
</pre>
 
</pre>
If you want to see the status of individual job steps you can use <code>squeue -s</code>
+
 
 
<pre>
 
<pre>
tgray26@shadosub:squeue -s
+
username@nexusclip00:squeue -s -u username
 
         STEPID    NAME PARTITION    USER      TIME NODELIST
 
         STEPID    NAME PARTITION    USER      TIME NODELIST
           162.0    sleep    test2 tgray26     0:05 shado00
+
           162.0    sleep    test2 username     0:05 tron00
           162.1    sleep    test2 tgray26     0:05 shado01
+
           162.1    sleep    test2 username     0:05 tron01
 
</pre>
 
</pre>
  
 
==sstat==
 
==sstat==
The sstat command shows metrics from currently running job steps. If you don't specify a job step the lowest job step is displayed.
+
The sstat command shows metrics from currently running job steps. If you don't specify a job step, the lowest job step is displayed.
 
<pre>
 
<pre>
 
sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize <$JOBID>.<$JOBSTEP>
 
sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize <$JOBID>.<$JOBSTEP>
 
</pre>
 
</pre>
 
<pre>
 
<pre>
tgray26@shadosub: sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 171
+
username@nexusclip00: sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 171
 
       JobID  NTasks            Nodelist    MaxRSS  MaxVMSize    AveRSS  AveVMSize  
 
       JobID  NTasks            Nodelist    MaxRSS  MaxVMSize    AveRSS  AveVMSize  
 
------------ -------- -------------------- ---------- ---------- ---------- ----------  
 
------------ -------- -------------------- ---------- ---------- ---------- ----------  
171.0              1             shado00         0    186060K          0    107900K  
+
171.0              1           tron00         0    186060K          0    107900K  
tgray26@shadosub: sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 171.1
+
username@nexusclip00: sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 171.1
 
       JobID  NTasks            Nodelist    MaxRSS  MaxVMSize    AveRSS  AveVMSize  
 
       JobID  NTasks            Nodelist    MaxRSS  MaxVMSize    AveRSS  AveVMSize  
 
------------ -------- -------------------- ---------- ---------- ---------- ----------  
 
------------ -------- -------------------- ---------- ---------- ---------- ----------  
171.1              1             shado01         0    186060K          0    107900K  
+
171.1              1           tron01         0    186060K          0    107900K  
 
</pre>
 
</pre>
Notice that if you do not have any jobsteps sstat will not return an error
+
Note that if you do not have any jobsteps, sstat will return an error.
 
<pre>
 
<pre>
tgray26@shadosub: sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 172
+
username@nexusclip00: sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 172
 
       JobID  NTasks            Nodelist    MaxRSS  MaxVMSize    AveRSS  AveVMSize  
 
       JobID  NTasks            Nodelist    MaxRSS  MaxVMSize    AveRSS  AveVMSize  
------------ -------- -------------------- ---------- ---------- ---------- ----------  
+
------------ -------- -------------------- ---------- ---------- ---------- ----------
sstat: error: no steps running for job 172
+
sstat: error: no steps running for job 237
 
</pre>
 
</pre>
If you do not run any srun commands you will not create any job steps and metrics will not be available for your job. Your batch scripts should follow this format
+
If you do not run any srun commands, you will not create any job steps and metrics will not be available for your job. Your batch scripts should follow this format:
 
<pre>
 
<pre>
 
#!/bin/bash
 
#!/bin/bash
Line 53: Line 64:
  
 
==sacct==
 
==sacct==
The sacct command shows metrics from past jobs
+
The sacct command shows metrics from past jobs.
 
<pre>
 
<pre>
tgray26@shadosub:sacct
+
username@nexusclip00:sacct
 
       JobID    JobName  Partition    Account  AllocCPUS      State ExitCode  
 
       JobID    JobName  Partition    Account  AllocCPUS      State ExitCode  
 
------------ ---------- ---------- ---------- ---------- ---------- --------  
 
------------ ---------- ---------- ---------- ---------- ---------- --------  
Line 66: Line 77:
 
163.0            sleep                staff          1  COMPLETED      0:0  
 
163.0            sleep                staff          1  COMPLETED      0:0  
 
</pre>
 
</pre>
To check one specific job you can run something like the following (if you omit <$JOBSTEP> all jobsteps will be shown:
+
To check one specific job, you can run something like the following (if you omit .<$JOBSTEP>, all jobsteps will be shown):
 
<pre>sacct  --format JobID,jobname,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize,Elapsed -j <$JOBID>.<$JOBSTEP></pre>
 
<pre>sacct  --format JobID,jobname,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize,Elapsed -j <$JOBID>.<$JOBSTEP></pre>
 
<pre>
 
<pre>
tgray26@shadosub:sacct  --format JobID,jobname,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize,Elapsed -j 171
+
username@nexusclip00:sacct  --format JobID,jobname,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize,Elapsed -j 171
 
       JobID    JobName  NTasks        NodeList    MaxRSS  MaxVMSize    AveRSS  AveVMSize    Elapsed  
 
       JobID    JobName  NTasks        NodeList    MaxRSS  MaxVMSize    AveRSS  AveVMSize    Elapsed  
 
------------ ---------- -------- --------------- ---------- ---------- ---------- ---------- ----------  
 
------------ ---------- -------- --------------- ---------- ---------- ---------- ---------- ----------  
171          helloWorld             shado[00-01]                                              00:00:30  
+
171          helloWorld           tron[00-01]                                              00:00:30  
171.batch        batch        1         shado00         0    119784K          0    113120K  00:00:30  
+
171.batch        batch        1       tron00         0    119784K          0    113120K  00:00:30  
171.0            sleep        1         shado00         0    186060K          0    107900K  00:00:30  
+
171.0            sleep        1       tron00         0    186060K          0    107900K  00:00:30  
171.1            sleep        1         shado01         0    186060K          0    107900K  00:00:30  
+
171.1            sleep        1       tron01         0    186060K          0    107900K  00:00:30  
 
</pre>
 
</pre>
 +
 +
=Job Codes=
 +
When you list the current running jobs and your job is in <code>PD</code> (Pending), SLURM will provide you some information on what the reason for this in the NODELIST parameter.  You can use <code>scontrol show job <jobid></code> to get all the parameters for your job which may be required to identify why your job is not running.
 +
 +
<pre>
 +
# squeue -u testuser
 +
JOBID PARTITION    NAME    USER    ST      TIME  NODES NODELIST(REASON)
 +
581530    dpart    bash    testuser PD      0:00      1 (AssocGrpGRES)
 +
581533    dpart    bash    testuser PD      0:00      1 (Resources)
 +
581534    dpart    bash    testuser PD      0:00      1 (QOSMaxGRESPerUser)
 +
581535    dpart    bash    testuser PD      0:00      1 (ReqNodeNotAvail, Reserved for maintenance)
 +
</pre>
 +
 +
Some common ones are as follows:
 +
* <code>Resources</code> - The cluster does not currently have the resources to fit your job.
 +
* <code>QOSMaxGRESPerUser</code> - The quality of service (QoS) your job is running in has a limit of resources per user.  Use <code>show_qos</code> to identify the limits and then use <code>scontrol show job <jobid></code> for each of your jobs running in that QoS.
 +
* <code>AssocGrpGRES</code> - The SLURM account you are using has a limit on the resources available in total for the account.  Use <code>sacctmgr show assoc account=<account_name></code> to identify the GrpTRES limit.  You can see all jobs running under the account by running <code>squeue -A account_name</code> and then find out more information on each job by <code>scontrol show job <jobid></code>.
 +
* <code>ReqNodeNotAvail</code> - You have requested a specific node for your job and it does not currently have the resources to fit your job.  Alternatively, if you also see <code>Reserved for maintenance</code>, there is a reservation in place (often for a [[MonthlyMaintenanceWindow | maintenance window]]).  You can see the current reservations by running <code>scontrol show reservation</code>.  Often the culprit is that you have requested a TimeLimit that will conflict with the reservation.  You can either lower your TimeLimit such that the job will complete before the reservation begins, or leave your job to wait until the reservation completes.

Latest revision as of 14:58, 22 September 2022

Job Status

SLURM offers a variety of tools to check the status of your jobs before, during, and after execution. When you first submit your job, SLURM should give you a job ID which represents the resources allocated to your job. Individual calls to srun will spawn job steps which can also be queried individually.

squeue

The squeue command shows job status in the queue. Helpful flags:

  • -u username to show only your jobs (replace username with your UMIACS username)
  • --start to estimate start time for a job that has not yet started and the reason why it is waiting
  • -s to show the status of individual job steps for a job (e.g. batch jobs)

Examples:

username@nexusclip00:squeue -u username
             JOBID PARTITION     NAME     USER ST       TIME  NODES NODELIST(REASON)
               162     test2 helloWor username  R       0:03      2 tron[00-01]
username@nexusclip00:squeue --start -u username
             JOBID PARTITION     NAME     USER ST          START_TIME  NODES SCHEDNODES           NODELIST(REASON)
               163     test2 helloWo2 username PD 2020-05-11T18:36:49      1 tron02            (Priority)
username@nexusclip00:squeue -s -u username
         STEPID     NAME PARTITION     USER      TIME NODELIST
          162.0    sleep     test2 username      0:05 tron00
          162.1    sleep     test2 username      0:05 tron01

sstat

The sstat command shows metrics from currently running job steps. If you don't specify a job step, the lowest job step is displayed.

sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize <$JOBID>.<$JOBSTEP>
username@nexusclip00: sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 171
       JobID   NTasks             Nodelist     MaxRSS  MaxVMSize     AveRSS  AveVMSize 
------------ -------- -------------------- ---------- ---------- ---------- ---------- 
171.0               1            tron00          0    186060K          0    107900K 
username@nexusclip00: sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 171.1
       JobID   NTasks             Nodelist     MaxRSS  MaxVMSize     AveRSS  AveVMSize 
------------ -------- -------------------- ---------- ---------- ---------- ---------- 
171.1               1            tron01          0    186060K          0    107900K 

Note that if you do not have any jobsteps, sstat will return an error.

username@nexusclip00: sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 172
       JobID   NTasks             Nodelist     MaxRSS  MaxVMSize     AveRSS  AveVMSize 
------------ -------- -------------------- ---------- ---------- ---------- ----------
sstat: error: no steps running for job 237

If you do not run any srun commands, you will not create any job steps and metrics will not be available for your job. Your batch scripts should follow this format:

#!/bin/bash
#SBATCH ...
#SBATCH ...
# set environment up
module load ...

# launch job steps
srun <command to run> # that would be step 1
srun <command to run> # that would be step 2

sacct

The sacct command shows metrics from past jobs.

username@nexusclip00:sacct
       JobID    JobName  Partition    Account  AllocCPUS      State ExitCode 
------------ ---------- ---------- ---------- ---------- ---------- -------- 
162          helloWorld      test2      staff          2  COMPLETED      0:0 
162.batch         batch                 staff          1  COMPLETED      0:0 
162.0             sleep                 staff          1  COMPLETED      0:0 
162.1             sleep                 staff          1  COMPLETED      0:0 
163          helloWorld      test2      staff          2  COMPLETED      0:0 
163.batch         batch                 staff          1  COMPLETED      0:0 
163.0             sleep                 staff          1  COMPLETED      0:0 

To check one specific job, you can run something like the following (if you omit .<$JOBSTEP>, all jobsteps will be shown):

sacct  --format JobID,jobname,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize,Elapsed -j <$JOBID>.<$JOBSTEP>
username@nexusclip00:sacct  --format JobID,jobname,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize,Elapsed -j 171
       JobID    JobName   NTasks        NodeList     MaxRSS  MaxVMSize     AveRSS  AveVMSize    Elapsed 
------------ ---------- -------- --------------- ---------- ---------- ---------- ---------- ---------- 
171          helloWorld           tron[00-01]                                               00:00:30 
171.batch         batch        1       tron00          0    119784K          0    113120K   00:00:30 
171.0             sleep        1       tron00          0    186060K          0    107900K   00:00:30 
171.1             sleep        1       tron01          0    186060K          0    107900K   00:00:30 

Job Codes

When you list the current running jobs and your job is in PD (Pending), SLURM will provide you some information on what the reason for this in the NODELIST parameter. You can use scontrol show job <jobid> to get all the parameters for your job which may be required to identify why your job is not running.

# squeue -u testuser
JOBID PARTITION     NAME     USER     ST       TIME  NODES NODELIST(REASON)
581530     dpart     bash    testuser PD       0:00      1 (AssocGrpGRES)
581533     dpart     bash    testuser PD       0:00      1 (Resources)
581534     dpart     bash    testuser PD       0:00      1 (QOSMaxGRESPerUser)
581535     dpart     bash    testuser PD       0:00      1 (ReqNodeNotAvail, Reserved for maintenance)

Some common ones are as follows:

  • Resources - The cluster does not currently have the resources to fit your job.
  • QOSMaxGRESPerUser - The quality of service (QoS) your job is running in has a limit of resources per user. Use show_qos to identify the limits and then use scontrol show job <jobid> for each of your jobs running in that QoS.
  • AssocGrpGRES - The SLURM account you are using has a limit on the resources available in total for the account. Use sacctmgr show assoc account=<account_name> to identify the GrpTRES limit. You can see all jobs running under the account by running squeue -A account_name and then find out more information on each job by scontrol show job <jobid>.
  • ReqNodeNotAvail - You have requested a specific node for your job and it does not currently have the resources to fit your job. Alternatively, if you also see Reserved for maintenance, there is a reservation in place (often for a maintenance window). You can see the current reservations by running scontrol show reservation. Often the culprit is that you have requested a TimeLimit that will conflict with the reservation. You can either lower your TimeLimit such that the job will complete before the reservation begins, or leave your job to wait until the reservation completes.