Thank you very much Sean! Your proposed solution solved the problem.
I reckon it's not very efficient, but works for us.
M.
To disable the backfill scheduler, add/change
SchedulerType=sched/builtin
in your slurm.conf, and restart your slurmctld. The default SchedulerType
is sched/backfill
In terms of it is bad that you don't specify the Timelimit for jobs
accurately, disabling backfill scheduler (and not specifying
>
> Can you see if it is set? Using (e.g. scontrol show job 337475 or sacct -j
> 337475 -o Timelimit)
>
At the moment my users don't set the TimeLimit, because they don't know how
long their jobs will take. If I check with sacct -o TimeLimit, I get :
Timelimit
--
365-00:00+
Is not
On Wed, 8 Jul 2020 at 00:47, zaxs84 wrote:
> *UoM notice: External email. Be cautious of links, attachments, or
> impersonation attempts.*
> --
> Hi Sean,
> thank you very much for your reply.
>
> > If a lower priority job can start AND finish before the resources a
>
Hi Sean,
thank you very much for your reply.
> If a lower priority job can start AND finish before the resources a
higher priority job requires are available, the backfill scheduler will
start the lower priority job.
That's very interesting, but how can the scheduler predict how long a
Hi,
What you have described is how the backfill scheduler works. If a lower
priority job can start AND finish before the resources a higher priority
job requires are available, the backfill scheduler will start the lower
priority job.
Your high priority job requires 24 cores, whereas the lower
