Hi Slurm gurus! I am observing following situation with SLURM_JOB_NODELIST variable. salloc, sbatch and srun launched under salloc declare SLURM_JOB_NODELIST. when srun executed directly does set SLURM_JOB_NODELIST
1) $salloc -N1 env | grep _NODELIST salloc: Granted job allocation 36858 salloc: Waiting for resource configuration salloc: Nodes mir4 are ready for job SLURM_JOB_NODELIST=tux1 SLURM_NODELIST=tux1 2) $cat check.slurm #!/bin/bash #SBATCH -N1 #SBATCH --ntasks-per-node=1 #SBATCH -t 1:00:00 env | grep _NODELIST $sbatch check.slurm SLURM_NODELIST=tux1 SLURM_JOB_NODELIST=tux1 3) $salloc -N1 srun env | grep _NODELIST salloc: Granted job allocation 36859 salloc: Waiting for resource configuration salloc: Nodes mir4 are ready for job SLURM_JOB_NODELIST=tux1 SLURM_NODELIST=tux1 SLURM_STEP_NODELIST=tux1 and $srun -N1 env | grep _NODELIST SLURM_NODELIST=mir4 SLURM_STEP_NODELIST=mir4 Can SLURM_NODELIST be used as an alternative of SLURM_JOB_NODELIST in all described cases? Regards, Igor
