you don't need to be a subscriber to search bugs.schedmd.com
On Tue, Dec 10, 2024 at 9:44 AM Davide DelVento via slurm-users
wrote:
>
> Good sleuthing.
>
> It would be nice if Slurm would say something like
> Reason=Priority_Lower_Than_Job_ so people will immediately find the
> culprit in s
Good sleuthing.
It would be nice if Slurm would say something like
Reason=Priority_Lower_Than_Job_ so people will immediately find the
culprit in such situations. Has anybody with a SchedMD subscription ever
asked something like that, or is there some reasons for which it'd be
impossible (or t
Found the problem: another job was blocking access to the reservation.
The strangest thing is that the node (gpu03) has always been reserved
for a project, the blocking job did not explicitly request it (and even
if it did, it would have been denied access) but its state was:
JobState=PENDING
Ciao Davide.
Il 06/12/2024 16:42, Davide DelVento ha scritto:
I find it extremely hard to understand situations like this. I wish
Slurm were more clear on how it reported what it is doing, but I digress...
I agree. A "scontrol explain" command could be really useful to pinpont
the cause :)
I
Ciao Diego,
I find it extremely hard to understand situations like this. I wish Slurm
were more clear on how it reported what it is doing, but I digress...
I suspect that there are other job(s) which have higher priority than this
one which are supposed to run on that node but cannot start because
