Thanks for this post - it's very interesting and most likely what I will move to once we have a system that does what we expect. At the moment, I'm certain that I've either: done something fundamentally wrong; discovered a bug or bugs in slurm; or have misunderstood something at a basic level.
I think I'll move it to a new thread because I now have more and better information, plus I've started with a "more correct" set up. Cheers L. ------ The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 29 September 2016 at 22:01, Janne Blomqvist <janne.blomqv...@aalto.fi> wrote: > On 2016-09-29 04:11, Lachlan Musicman wrote: > > Hi, > > > > After some fun incidents with accidental monopolization of the cluster, > > we decided to enforce some QOS. > [snip] > > What have I done wrong? I re-read the documentation this AM, but I can't > > see anything that might be preventing QOS from being applied except for > > maybe a qos hierarchy issue, but I've only set the two qos and they > > apply to distinct associations and partitions. > > What you actually want here is GrpTRESRunMins, see > http://tech.ryancox.net/2014/04/scheduler-limit-remaining-cputime-per.html > for an explanation how it works. > > Also, if you do this you'll probably want to add "safe" to your > AccountingStorageEnforce flags. > > > -- > Janne Blomqvist, D.Sc. (Tech.), Scientific Computing Specialist > Aalto University School of Science, PHYS & NBE > +358503841576 || janne.blomqv...@aalto.fi > >
