BTW, I should have mentioned we are using 16.05.7. Thanks for the info Chris. I don't think this is a backfill problem. These are jobs that should start regardless of backfill – they are top priority jobs that have free resources available. We are using the default backfill options but those should be fine for us. The default backfill queue depth is 100 jobs and we normally have less than 100 total jobs in the queue at a given time.
Can you point me to some info on the plugins and filters you mentioned? I'm having trouble finding info on them. -----Original Message----- From: Christopher Samuel <[email protected]> Reply-To: slurm-dev <[email protected]> Date: Wednesday, February 8, 2017 at 5:32 PM To: slurm-dev <[email protected]> Subject: [slurm-dev] Re: Job priority/cluster utilization help On 08/02/17 11:19, Vicker, Darby (JSC-EG311) wrote: > Sorry for the long post but not sure how to get adequate help without > providing a lot of detail. Any recommendations on configuring the > scheduler to help these jobs run and increase the cluster utilization > would be appreciated. My one thought after a quick scan is that both the jobs you mention are listed as reason "Priority" and there's a higher priority job 1772 in the list before them. You might want to look at your backfill settings to see whether it's looking far enough down the queue to see these. Perhaps an alternative idea would be to instead of using features use partitions and then have people submit to all partitions (there is a plugin for that, though we use a submit filter instead to accomplish the same). That way Slurm should consider each job against each partition (set of architectures) individually. Best of luck! Chris -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci
