You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, it is obvious why this is happening, Amarel uses an old version of SLURM (18.0.8) which if you check the archive documentation (https://slurm.schedmd.com/archive/slurm-18.08.8/srun.html) they do not support the flag --nodefile. How should we proceed? should we support backward compatibility of the old version of SLURM?
The text was updated successfully, but these errors were encountered:
Per discussion on the devel call, we should be switching to --nodelist as that is faster (less file I/O). We are limited to the max number of command line characters though, and beyond that need to switch to --nodefile for the command to work at all. In that case Amarel is out of luck. We should address that case only once there is a use case / user requesting it. Mikhael suggested to look into env variables also to work around the command length limit.
Based on the PR #2448, RP is failing on Amarel for the following reason:
/usr/bin/srun: unrecognized option '--nodefile=/home/afa64/radical.pilot.sandbox/rp.session.amarel2.amarel.rutgers.edu.afa64.018907.0010/pilot.0000/task.000013//task.000013.nodes'
Now, it is obvious why this is happening, Amarel uses an old version of SLURM (18.0.8) which if you check the archive documentation (https://slurm.schedmd.com/archive/slurm-18.08.8/srun.html) they do not support the flag
--nodefile
. How should we proceed? should we support backward compatibility of the old version of SLURM?The text was updated successfully, but these errors were encountered: