This is what I would expect. It doesn't matter that the 7 license job has
higher priority as it in ineligible to run due to the lack of licenses. The
scheduler moves on and prioritises (and starts) the next eligible job.
I will suggest a workaround. You could periodically run a script that look
Depending on other variables, it is fine.
The 7 license job cannot run because there are only 5 available, so that
one has to wait.
Since there are 5 available, the 1 license job can run, so it does.
That is the simple view. Other variables such as job time could affect that.
Brian Andrus
On
We have a group of users who occasionally report seeing jobs start without,
for example, $HOME being set.
Looking at the slurmd logs (info level) on our 20.11.8 node, shows the first
instance of an afflicted JobID appearing as
[2022-03-11T00:19:35.117] task/affinity: task_p_slurmd_batch_request:
