The problem has been solved. We tested it with ’srun’ and that did not work the
same is for ’salloc’ To make it work with these commands apply one of the
solutions:
1. Add ‘defer’ to ScheduleParameters
2. srun --begin=now+1
sbatch works out of the box. Thanks to schedmd (Ben) for the solu
Still have this question. Sometime we have free nodes and users that are
allowed to run in the MAGNETIC reservation are first scheduled on the
free nodes instead of reservation nodes. Dit I forgot an option or is
this the expected behavior?
On 25/09/2020 16:47, Bas van der Vlies wrote:
Ar
Thanks Troy,
That is our intention also for course/training purposes if there are course
days.
regards
--
Bas van der Vlies
| Operations, Support & Development | SURFsara | Science Park 140 | 1098 XG
Amsterdam
| T +31 (0) 20 800 1300 | bas.vandervl...@surf.nl | www.surf.nl |
> On 25 Se
I've been looking at it for classroom type reservations, but I ran into a bug
where jobs that weren't eligible to access the reservation were being attracted
to it anyway. That's supposed to be fixed in 20.02.6. See
https://bugs.schedmd.com/show_bug.cgi?id=9593 for details.
--Troy
O
Are people using the MAGNETIC reservation flag? My question would be how?
because to my it would be more useful if the reservation is tried first and
then the free nodes.
That is what I expected with the MAGNETIC flag.
Bas van der Vlies
| Operations, Support & Development | SURFsara | Science
We have installed slurm 20.02.5 and I am trying to use this new reservation flag
MAGNETIC:
* https://slurm.schedmd.com/reservations.html
From this page I understand that the job will land in the reservation even if we
did not specify the
reservation name. I tested it on our cluster setup but i
