Scheduler Fundamentals

Overview

Teaching: 35 min
Exercises: 30 min

Questions

• What is a scheduler and why does a cluster need one?

• How do I launch a program to run on a compute node in the cluster?

• How do I capture the output of a program that is run on a node in the cluster?

Objectives

• Submit a simple script to the cluster.

• Monitor the execution of jobs using command line tools.

• Inspect the output and error files of your jobs.

• Use compute nodes interactively for resource intensive tasks.

Job Scheduler

An HPC system might have thousands of nodes and users. How do we decide who gets what and when? How do we ensure that a task is run with the resources it needs? This job is handled by a special piece of software called the scheduler. On an HPC system, the scheduler manages which jobs run where and when.

The following illustration compares these tasks of a job scheduler to a waiter in a restaurant. If you can relate to an instance where you had to wait for a while in a queue to get in to a popular restaurant, then you may now understand why sometimes your job does not start instantly as in your laptop.

The scheduler used in this lesson is Slurm. Although Slurm is not used everywhere, running jobs is quite similar regardless of what software is being used. The exact syntax might change, but the concepts remain the same.

Running a Batch Job

The most basic use of the scheduler is to run a command non-interactively. Any command (or series of commands) that you want to run on the cluster is called a job, and the process of using a scheduler to run the job is called batch job submission.

In this case, the job we want to run is a shell script – essentially a text file containing a list of UNIX commands to be executed in a sequential manner. Our shell script will have three parts:

• On the very first line, add #!/usr/bin/env bash. The #! (pronounced “hash-bang” or “shebang”) tells the computer what program is meant to process the contents of this file. In this case, we are telling it that the commands that follow are written for the command-line shell (what we’ve been doing everything in so far).
• Anywhere below the first line, we’ll add an echo command with a friendly greeting. When run, the shell script will print whatever comes after echo in the terminal.
  • echo -n will print everything that follows, without ending the line by printing the new-line character.
• On the last line, we’ll invoke the hostname command, which will print the name of the machine the script is run on.

First open your new script in a text editor:

[yourUsername@borah-login ~]$ nano example-job.sh

#!/usr/bin/env bash

echo -n "This script is running on "
hostname

Creating Our Test Job

Run the script. Does it execute on the cluster or just our login node?

Solution

[yourUsername@borah-login ~]$ bash example-job.sh

This script is running on borah-login

This script ran on the login node, but we want to take advantage of the compute nodes: we need the scheduler to queue up example-job.sh to run on a compute node.

To submit this task to the scheduler, we use the sbatch command. This creates a job which will run the script when dispatched to a compute node which the queuing system has identified as being available to perform the work.

[yourUsername@borah-login ~]$ sbatch --partition=bsudfq example-job.sh

Submitted batch job 36855

And that’s all we need to do to submit a job. Our work is done – now the scheduler takes over and tries to run the job for us. While the job is waiting to run, it goes into a list of jobs called the queue. To check on our job’s status, we check the queue using the command squeue --me.

[yourUsername@borah-login ~]$ squeue --me

 JOBID PARTITION     NAME     ST       TIME  NODES NODELIST(REASON)
 36855    bsudfq example-      R       0:05      1 cpu116

We can see all the details of our job, most importantly that it is in the R or RUNNING state. Sometimes our jobs might need to wait in a queue (PENDING) or have an error (E).

Where’s the Output?

On the login node, this script printed output to the terminal – but now, when squeue shows the job has finished, nothing was printed to the terminal.

Cluster job output is typically redirected to a file in the directory you launched it from. Use ls to find and cat to read the file.

Customising a Job

The job we just ran used all of the scheduler’s default options. In a real-world scenario, that’s probably not what we want. The default options represent a reasonable minimum. Chances are, we will need more cores, more memory, more time, among other special considerations. To get access to these resources we must customize our job script.

Comments in UNIX shell scripts (denoted by #) are typically ignored, but there are exceptions. For instance the special #! comment at the beginning of scripts specifies what program should be used to run it (you’ll typically see #!/usr/bin/env bash). Schedulers like Slurm also have a special comment used to denote special scheduler-specific options. Though these comments differ from scheduler to scheduler, Slurm’s special comment is #SBATCH. Anything following the #SBATCH comment is interpreted as an instruction to the scheduler.

Let’s illustrate this by example. By default, a job’s name is the name of the script, but the -J option can be used to change the name of a job. Add an option to the script:

[yourUsername@borah-login ~]$ cat example-job.sh

#!/usr/bin/env bash
#SBATCH -J hello-world

echo -n "This script is running on "
hostname

Submit the job and monitor its status:

[yourUsername@borah-login ~]$ sbatch --partition=bsudfq example-job.sh
[yourUsername@borah-login ~]$ squeue --me

 JOBID PARTITION     NAME     ST       TIME  NODES NODELIST(REASON)
212202    bsudfq hello-wo      R       0:02      1 cpu101

Fantastic, we’ve successfully changed the name of our job!

Resource Requests

What about more important changes, such as the number of cores and memory for our jobs? One thing that is absolutely critical when working on an HPC system is specifying the resources required to run a job. This allows the scheduler to find the right time and place to schedule our job. If you do not specify requirements (such as the amount of time you need), you will likely be stuck with your site’s default resources, which is probably not what you want.

The following are several key resource requests:

• --cpus-per-task=<ncpus> or -c <ncpus>: How many CPU cores does each task need? Useful for applications using shared memory parallelism, e.g., OpenMP.

• --ntasks=<ntasks> or -n <ntasks>: How many tasks will your job use? Useful for applications using distributed parallelism, e.g., MPI.

• --time <days-hours:minutes:seconds> or -t <days-hours:minutes:seconds>: How much real-world time (walltime) will your job take to run? The <days> part can be omitted.

• --mem=<megabytes>: How much memory on a node does your job need in megabytes? You can also specify gigabytes using by adding a little “g” afterwards (example: --mem=5g)

• --gres=gpu:<ngpu>: How many gpus does your job need? Make sure you are submitting to a partition with gpus, e.g. --partition=gpu or --partition=shortgpu.

• --nodes=<nnodes> or -N <nnodes>: How many separate machines does your job need to run on? Note that if you set ntasks to a number greater than what one machine can offer, Slurm will set this value automatically.

Note that just requesting these resources does not make your job run faster, nor does it necessarily mean that you will consume all of these resources. It only means that these are made available to you. Your job may end up using less memory, or less time, or fewer nodes than you have requested, and it will still run.

It’s best if your requests accurately reflect your job’s requirements. We’ll talk more about how to make sure that you’re using resources effectively in a later episode of this lesson.

Submitting Resource Requests

Modify our hostname script so that it runs for a minute, then submit a job for it on the cluster.

Solution

[yourUsername@borah-login ~]$ cat example-job.sh

#!/usr/bin/env bash
#SBATCH -t 00:01 # timeout in HH:MM

echo -n "This script is running on "
sleep 20 # time in seconds
hostname

[yourUsername@borah-login ~]$ sbatch --partition=bsudfq example-job.sh

Why are the Slurm runtime and sleep time not identical?

Job environment variables

When Slurm runs a job, it sets a number of environment variables for the job. One of these will let us check what directory our job script was submitted from. The SLURM_SUBMIT_DIR variable is set to the directory from which our job was submitted. Using the SLURM_SUBMIT_DIR variable, modify your job so that it prints out the location from which the job was submitted.

Solution

[yourUsername@borah-login ~]$ cat example-job.sh

#!/usr/bin/env bash
#SBATCH -t 00:00:30

echo -n "This script is running on "
hostname

echo "This job was launched in the following directory:"
echo ${SLURM_SUBMIT_DIR}

Resource requests are typically binding. If you exceed them, your job will be killed. Let’s use wall time as an example. We will request 1 minute of wall time and attempt to run a job for two minutes.

[yourUsername@borah-login ~]$ cat example-job.sh

#!/usr/bin/env bash
#SBATCH -J long_job
#SBATCH -t 00:01 # timeout in HH:MM

echo "This script is running on ... "
sleep 240 # time in seconds
hostname

Submit the job and wait for it to finish. Once it is has finished, check the log file.

[yourUsername@borah-login ~]$ sbatch --partition=bsudfq example-job.sh
[yourUsername@borah-login ~]$ squeue --me

[yourUsername@borah-login ~]$ cat slurm-38193.out

This job is running on ...

slurmstepd: error: *** JOB 38193 ON cpu116 CANCELLED AT
2023-03-28T16:35:48 DUE TO TIME LIMIT ***

Our job was killed for exceeding the amount of resources it requested. Although this appears harsh, this is actually a feature. Strict adherence to resource requests allows the scheduler to find the best possible place for your jobs. Even more importantly, it ensures that another user cannot use more resources than they’ve been given. If another user messes up and accidentally attempts to use all of the cores or memory on a node, Slurm will either restrain their job to the requested resources or kill the job outright. Other jobs on the node will be unaffected. This means that one user cannot mess up the experience of others, the only jobs affected by a mistake in scheduling will be their own.

Cancelling a Job

Sometimes we’ll make a mistake and need to cancel a job. This can be done with the scancel command. Let’s submit a job and then cancel it using its job number (remember to change the walltime so that it runs long enough for you to cancel it before it is killed!).

[yourUsername@borah-login ~]$ sbatch --partition=bsudfq example-job.sh
[yourUsername@borah-login ~]$ squeue --me

Submitted batch job 212203

 JOBID PARTITION     NAME     ST       TIME  NODES NODELIST(REASON)
212203    bsudfq hello-wo      R       0:03      1 cpu101

Now cancel the job with its job number (printed in your terminal). A clean return of your command prompt indicates that the request to cancel the job was successful.

[yourUsername@borah-login ~]$ scancel 212203
# It might take a minute for the job to disappear from the queue...
[yourUsername@borah-login ~]$ squeue --me

 JOBID PARTITION     NAME     USER ST       TIME  NODES NODELIST(REASON)

Cancelling multiple jobs

We can also cancel all of our jobs at once using the --me option. This will delete all jobs for a specific user (in this case, yourself). Note that you can only delete your own jobs.

Try submitting multiple jobs and then cancelling them all.

Solution

First, submit a trio of jobs:

[yourUsername@borah-login ~]$ sbatch --partition=bsudfq example-job.sh
[yourUsername@borah-login ~]$ sbatch --partition=bsudfq example-job.sh
[yourUsername@borah-login ~]$ sbatch --partition=bsudfq example-job.sh

Then, cancel them all:

[yourUsername@borah-login ~]$ scancel --me

Interactive jobs

Up to this point, we’ve focused on running jobs in batch mode. Slurm also provides the ability to start an interactive session.

There are very frequently tasks that need to be done interactively. Creating an entire job script might be overkill, but the amount of resources required is too much for a login node to handle. A good example of this might be building a genome index for alignment with a tool like HISAT2. Fortunately, we can run these types of tasks using dev-session, a shortcut which opens a bash terminal on a compute node.

[yourUsername@borah-login ~]$ dev-session

You should be presented with a bash prompt. Note that the prompt will likely change to reflect your new location, in this case the compute node we are logged on. You can also verify this with hostname.

When you are done with the interactive job, type exit or ctrl + D to quit your session.

Key Points

• The scheduler handles how compute resources are shared between users.

• A job is just a shell script.

• Request slightly more resources than you will need.