[slurm-dev] Changed behaviour of --exclusive in srun (job step context)

[Magnus Jonsson]

Hi!

A user found a "strange" new behaviour when using --exclusive with srun.

I have an example submit-script[1] that shows this.

I have tested this on 2.6.4 with the output [2] & [3] (stderr) and on
14.03.7 with the output [4] & [5] (stderr).

In 14.03.7 without --exclusive behaves like 2.6.4 with --exclusive.





If you need more information please let me know.

Best regards,
Magnus

1, http://www.hpc2n.umu.se/staff/magnus/slurm/submit.sh
2, http://www.hpc2n.umu.se/staff/magnus/slurm/stdout.2.6.4
3, http://www.hpc2n.umu.se/staff/magnus/slurm/stderr.2.6.4
4, http://www.hpc2n.umu.se/staff/magnus/slurm/stdout.14.03.7
5, http://www.hpc2n.umu.se/staff/magnus/slurm/stderr.14.03.7

--
Magnus Jonsson, Developer, HPC2N, Umeå Universitet

In 14.03.7 with --exclusive get some kind of "node exclusive" within the job. --overcommit gets the same behaviour on both versions. in 14.03.7 -c3 does not seams to work at all in job step context I see warnings about this in the man page for srun but in 2.6.4 this works as I aspect. Stderr output from srun: "srun: error: Unable to create job step: Requested node configuration is not available"

smime.p7s
Description: S/MIME Cryptographic Signature