At CCNI, we use backfill scheduling on all our systems. However, we have
found that users typically do not specify a time limit for their job so
the scheduler assumes the maximum from QoS/user limits/partition
limits/etc. This really hurts backfilling since the scheduler remains
ignorant of short j
An alternative that we do is choose very low defaults for people:
PartitionName=Default DefaultTime=30:00 #plus other options
DefMemPerCPU=512
The disadvantage to this approach is that it doesn't give an obvious
error message at submit time. However, it's not hard to figure out what
h
Hi Ryan,
Thanks. We had considered this approach but went in a different
direction for a couple reasons:
We have a good number of users that script job submissions and may blast
out up to several hundred jobs. A user might not realize their jobs are
getting cutoff until many of them run and it's
Hello,
Why not enable this functionality by setting DefaultTime=0 in slurm.conf which
would let us set this on per-partition basis, rather than through job submit
plugin. (Unless i'm missing something obvious here)
Also currently setting DefaultTime=0 (on 2.5.6 at least) gives following
mess
Another route that could be taken is to set the DefaultTime for a
partition to 0, and the
small patch attached to this email will reject a job when is has no time
limit specified
and the default_time limit is 0. I also modified the
ESLURM_INVALID_TIME_LIMIT
to include information that the error mig
