...
...
|
This page gives a basic introduction to the O2 cluster for new cluster users. Reading this page will help you to submit interactive and batch jobs to the Slurm scheduler on O2, as well as teach you how to monitor and troubleshoot your jobs as needed.
...
Note: Any time <userid> is mentioned in this document, it should be replaced with your HMS account, formerly called an eCommons ID (and omit the <>). Likewise, <jobid> should be replaced with an actual job ID, such as 12345. The name of a batch job submission script should be inserted wherever <jobscript> is mentioned.
SLURM command | Sample command syntax | Meaning |
|---|---|---|
| sbatch | sbatch <jobscript> | Submit a batch (non-interactive) job. |
| srun | srun --pty -t 0-0:5:0 -p interactive /bin/bash | Start an interactive session for five minutes in the interactive queue. |
| squeue | squeue -u <userid> | View status of your jobs in the queue. Only non-completed jobs will be shown. We have an easier-to-use alternative command called O2squeue. |
| scontrol | scontrol show job <jobid> | Look at a running job in detail. For more information about the job, add the -dd parameter. |
| scancel | scancel <jobid> | Cancel a job. scancel can also be used to kill job arrays or job steps. |
| scontrol | scontrol hold <jobid> | Pause a job |
| scontrol | scontrol release <jobid> | Release a held job (allow it to run) |
| sacct | sacct -j <jobid> | Check job accounting data. Running We have an easier-to-use alternative command called O2sacct. |
| sinfo | sinfo | See node and partition information. Use the -N parameter to see information per node. |
...