Thanks to all for the tips! They will definitely make our lives easier. However, this isn't really the ideal solution. One drawback is that a job that started running in the checkpointed low priority queue will stay there until it finishes even if a slot becomes available in the high priority queue. In principle, there is no need for two queues. So I still think the ideal scheduler would do this with one queue. Nevertheless, thanks for the great development and support!
Eyal On Sep 23, 2014 7:54 PM, "Danny Auble" <[email protected]> wrote: > > Or just use the all_partitions job_submit plugin. > > On 09/23/2014 09:52 AM, Kilian Cavalotti wrote: > >> Hi, >> >> On Tue, Sep 23, 2014 at 7:18 AM, Yann Sagon <[email protected]> wrote: >> >>> To lower the problem of having to deal with two queues, you can specify >>> the two queues like that when you submit a job : --partition=queue1,queue2 >>> and the first one that is free is selected. >>> >> You can even define an env variable in users' environment so they >> don't have to type anything. "export SLURM_PARTITION=queue1,queue2" >> would do the same. Note that for sbatch, it's SBATCH_PARTITION, and >> SALLOC_PARTITION for salloc. >> >> Cheers, >> >
