Loris,
Taking Slurm v2.3 as a data point, the sbatch behavior seems consistent with
what you report for v16.05.
I deliberately attempted to request fewer nodes than I specified with the
--nodelist option (attempting the potential behavior you describe below) and
sbatch complained:
$ sbatch -N2 --wrap hostname --nodelist=cab[2-5] -p pdebug
sbatch: error: Batch job submission failed: Node count specification invalid
I had to specify a node count that matched the nodelist-specified node count or
omit the –N spec for it to succeed:
$ sbatch --wrap hostname --nodelist=cab[2-5] -p pdebug
Submitted batch job 2857543
$ sbatch -N4 --wrap hostname --nodelist=cab[10-13] -p pdebug
Submitted batch job 2857564
$ sacct -X -j 2857543,2857564 -o jobid,nnodes,nodelist
JobID NNodes NodeList
------------ -------- ---------------
2857543 4 cab[2-5]
2857564 4 cab[10-13]
Don
On 7/26/17, 1:59 AM, "Loris Bennett" <[email protected]> wrote:
Hi,
With Version 16.05.10-2
--nodelist
seems to be a list of nodes which are *all* assigned to the job. In
previous versions I seem to remember it being complementary to
--exclude
i.e. a list of *potential* nodes for the job.
Is this correct and, if so, are there any plans to reintroduce the old
functionality, say, with a option '--include'?
Cheers,
Loris
--
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin Email [email protected]
