Hi Eva,
if you don't want to use the controller node for jobs, the easiest way
is to not configure it as node at all. Meaning you don't need a line like
NodeName=hpc-0-5 RealMemory=....
for the controller.
A program/user can find out which nodes are allocated by looking into
the environment variables. Try running salloc and then
$ env | grep SLURM
Here is an example output:
SLURM_NODELIST=n523601
SLURM_NODE_ALIASES=(null)
SLURM_NNODES=1
SLURM_JOBID=6437
SLURM_TASKS_PER_NODE=40
SLURM_JOB_ID=6437
SLURM_SUBMIT_DIR=/nfs/admins/adm17
SLURM_JOB_NODELIST=n523601
SLURM_JOB_CPUS_PER_NODE=40
SLURM_SUBMIT_HOST=frontend
SLURM_JOB_PARTITION=foo
SLURM_JOB_NUM_NODES=1
Regards,
Uwe
Am 12.09.2014 um 00:45 schrieb Eva Hocks:
>
>
>
> I am trying to configure the latest slurm 14.03 and am running into
> problem to prevent slurm from running jobs on the control node.
>
> sinfo shows 3 nodes configure in the slurm.conf:
> active up 2:00:00 1 down* hpc-0-5
> active up 2:00:00 1 mix hpc-0-4
> active up 2:00:00 1 idle hpc-0-6
>
>
> but when I use salloc I end up on the head node
>
>
> $ salloc -N 1 -p active sh
> salloc: Granted job allocation 16
> sh-4.1$ hostname
> hpcdev-005.sdsc.edu
>
>
> That node is not part of the "active" partition but slurm still uses it.
> How? The allocation btw is for NodeList=hpc-0-4
> and the user can login to that node without a problem but slurm doesn't
> run the sh on that node for the user.
>
> Also how can a user find out what nodes are allocated without having to
> run the scontrol command? Is there an option in salloc to return the
> host names?
>
> Thanks
> Eva
>
