Sounds good, thanks! Eyal On Sep 23, 2014 5:18 PM, "Yann Sagon" <[email protected]> wrote:
> > > 2014-09-22 23:37 GMT+02:00 Eyal Privman <[email protected]>: > >> Hi, >> >> >> I know some places implement a policy where each group owns a >> high-priority queue for its share of nodes and a public low-priority queue >> allows anyone to run on the unused nodes. This public queue is checkpointed >> to allow jobs to be evicted by the node owner and later resumed. However, >> this solution requires each user to manually split their jobs between the >> private and public queues, to monitor their progress, and to redistribute >> jobs between the queues if one queue is slower than expected. It's >> desirable that SLURM would automatically manage this without the >> complication of having two queues. I.e. everybody submits to one queue and >> the smart scheduler manages everything so that every group gets its fair >> share at any moment, instantaneously thanks to checkpointing. Is such a >> solution possible? >> >> > 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. > >
