Il 01/06/2021 15:37, Brian Andrus ha scritto:
Tks Brian and Marcus.
Seems I misinterpreted the docs.
We need to target one of two identical nodes for performance comparisons
between runs (students have to learn how to scale their jobs).
I'll have to use a feature, since it seems requesting a
That is expected behavior as Marcus pointed out.
I suspect you may be doing something like targeting one of two systems
that each have a node-locked license for some software, or have some
different specs.
In this case, you may want to use the FEATURES option when defining
those nodes and
Hi,
as per
https://slurm.schedmd.com/archive/slurm-18.08.5/sbatch.html#OPT_nodelist
Request a specific list of hosts. The job will contain *all* of these hosts and
possibly additional hosts as needed to satisfy resource requirements.
So at least in the sbatch manpage it explicitly states
Hello all.
I just found that if an user tries to specify a nodelist (say including
2 nodes) and --nodes=1, the job gets rejected with
sbatch: error: invalid number of nodes (-N 2-1)
The expected behaviour is that slurm schedules the job on the first node
available from the list.
I've found
