A job consists of one or more steps, each consisting of one or more tasks each using one or more CPU. Jobs are typically created with the sbatch command, steps are created with the srun command, tasks are requested, at the job level with –ntasks or –ntasks-per-node, or at the step level with –ntasks. CPUs … Read more
It means no further job will be scheduled on that node, but the currently running jobs will keep running (by contrast with setting the node down which kills all jobs running on the node). Nodes are often set to that state so that some maintenance operation can take place once all running jobs are finished. … Read more
You should use the format option, with: sacct –helpformat you’ll see the parameters to show, for instance: sacct –format=”JobID,JobName%30″ will print the job id and the name up to 30 characters: JobID JobName ———— —————————— 19009 bash 19010 launch.sh 19010.0 hydra_pmi_proxy 19010.1 hydra_pmi_proxy Now, you can to customize your own output.
I thought I’d offer some insight because I was also looking for the replacement to the -v option in qsub, which for sbatch can be accomplished using the –export option. I found a nice site here that shows a list of conversions from Torque to Slurm, and it made the transition much smoother. You can … Read more
The –ntasks parameter is useful if you have commands that you want to run in parallel within the same batch script. This may be two separate commands separated by an & or two commands used in a bash pipe (|). For example Using the default ntasks=1 #!/bin/bash #SBATCH –ntasks=1 srun sleep 10 & srun sleep … Read more
If your job is finished, then the sacct command is what you’re looking for. Otherwise, look into sstat. For sacct the –format switch is the other key element. If you run this command: sacct -e you’ll get a printout of the different fields that can be used for the –format switch. The details of each … Read more
Use the scontrol command to modify a job scontrol update jobid=<job_id> TimeLimit=<new_timelimit> Use the SLURM time format, eg. for 8 days 15 hours: TimeLimit=8-15:00:00 Requires admin privileges, on some machines. Will be allowed to users only if the job is not running yet, on most machines.
The documentation says srun is used to submit a job for execution in real time while sbatch is used to submit a job script for later execution. They both accept practically the same set of parameters. The main difference is that srun is interactive and blocking (you get the result in your terminal and you … Read more