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 happened when they hit the time limit or the error output says they went over their memory limit.
Ryan On 06/28/2013 08:29 AM, Daniel M. Weeks wrote:
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 jobs. Attached is a small patch I wrote containing a job submit plugin and a new error message. The plugin rejects a job submission when it is missing a time limit and will provide the user with a clear and distinct error. I've just re-tested and the patch applies and builds cleanly on the slurm-2.5, slurm-2.6, and master branches. Please let me know if you find this useful, run across problems, or have suggestions/improvements. Thanks.
-- Ryan Cox Operations Director Fulton Supercomputing Lab Brigham Young University
