Yes.. but I fail to see the absence. I say that I want 8 tasks per node and not 16.
If say I want the node exclusive should not invalidate that in my opinion.As a basic rule we tell our users to not think of nodes and think in terms of task and Slurm will give them the number of nodes they need.
This might not be true for more advanced users/use cases but Best regards, Magnus On 2014-02-19 15:49, Rod Schultz wrote:
In the absence of other directives, slurm tries to use the minimum number of nodes. Instead of -n16, try -N 2 That tells slurm to use two nodes. Here's a demo case srun -l -N2 --tasks-per-node=2 hostname 1: trek0 0: trek0 2: trek1 3: trek1 -----Original Message----- From: Magnus Jonsson [mailto:[email protected]] Sent: Wednesday, February 19, 2014 1:28 AM To: slurm-dev Subject: [slurm-dev] --exclusive together with --ntasks-per-node not working as expected. Hi! We have a user that submitted a job that did not start as expected. He was using --exclusive together with --ntasks-per-node but ended up with all task on one node anyway. ----8<---- #SBATCH -n 16 #SBATCH --exclusive #SBATCH --ntasks-per-node=8 ----8<---- See the attached files for more information about how the job was submitted. We are currently running version 2.6.3. Best regards, Magnus
-- Magnus Jonsson, Developer, HPC2N, Umeå Universitet
smime.p7s
Description: S/MIME Cryptographic Signature
