BRC Cluster Workshop

User Tools

Site Tools

Trace:
sbatch

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
sbatch [2021/05/21 11:24]
root 		sbatch [2021/10/22 12:05] (current)
root
Line 1: Line 1:
 ====== sbatch ====== ====== sbatch ======
  
-**sbatch** submits a script to be executed to the slurm controller and returns immediately. The script may be queued for running later if there are currently no resources (cores) available to run it. The script is "detached" from your terminal, so even if you log out it will run, or continue to run.+**sbatch** submits a script to be executed to the slurm controller and returns immediately. The script may be queued for running later if there are currently no resources (cores or memory) available to run it. The script is "detached" from your terminal, so even if you log out it will run, or continue to run.
  
 The working directory for the script will be set to the current working directory when you submit the job. The working directory for the script will be set to the current working directory when you submit the job.
Line 50: Line 50:
  
 sbatch -N4 ex1.bash one two sbatch -N4 ex1.bash one two
 +
 +** Unless you intend to use srun from within your script, the -N option is probably not what you want. **
  
 The "-N4" option requests an allocation of 4 nodes for this job. **sbatch** only runs the script once. What it is doing is allocating 4 nodes and running the script on the first one. Tasks can be run on the allocated nodes by using srun from within your script. The "-N4" option requests an allocation of 4 nodes for this job. **sbatch** only runs the script once. What it is doing is allocating 4 nodes and running the script on the first one. Tasks can be run on the allocated nodes by using srun from within your script.
Line 99: Line 101:
 </code> </code>
  
-If you have submitted an array job and change your mind about how many of the array tasks should be running at any one time (perhaps the cluster gets less busy so it seems reasonable to change the number of jobs you are running at one time), you can use scontrol to do that.+If you have submitted an array job and change your mind about how many of the array tasks should be running at any one time (perhaps the cluster gets less busy so it seems reasonable to increase the number of jobs you are running at one time), you can use scontrol to do that.
  
 <code> <code>
Line 105: Line 107:
 </code> </code>
  
 +You can cancel all of an array job in one go by using scancel on the job number of the array job entry. You can also cancel the individual tasks submitted by the array job.
 +
 +To cancel the entire job (including all running tasks):
 +
 +<code>
 +scancel NNNNNNN
 +</code>
 +
 +To cancel an individual task from the array job (in this case task number 2):
 +
 +<code>
 +scancel NNNNNNN_2
 +</code>
 +
 +You can also cancel a range of the individual tasks within the array as follows. This will work whether the tasks are already running or not.
 +
 +<code>
 +scancel NNNNNNN_[9-19]
 +</code>
  
sbatch.1621610661.txt.gz ยท Last modified: 2021/05/21 11:24 by root

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
Public Domain Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki