When I tried that, it looks like I end up with a default of maxjobs=<whatever> for each of the account/user associations.
I tried setting the cluster maxjobs=2 and submitted 6 jobs through one account and only two of them started. Submitting another 6 jobs with the same userid with another account allowed another two jobs to start from that account. Does it work differently for you? I was looking for something that limited a user jobs regardless of how many accounts they're on. ----- Gary Skouson -----Original Message----- From: Chris Samuel [mailto:[email protected]] Sent: Thursday, February 18, 2016 4:57 PM To: slurm-dev <[email protected]> Subject: [slurm-dev] RE: max user jobs limit? On Thu, 18 Feb 2016 02:46:20 PM Skouson, Gary B wrote: > As far as I can tell, there isn’t really a way to set a default combined > limit across the cluster for the jobs a particular user can run You can! We do: sacctmgr modify cluster ${CLUSTER} set maxjobs=192 We thought we had to use QoS for this as well, but it's a bad idea as that takes priority over so many other things. The reason we'd missed it before is not realising the significance of: # NOTE: You can also use the general specifications list above in the # GENERAL SPECIFICATIONS FOR ASSOCIATION BASED ENTITIES section. in the section on cluster specifications in the sacctmgr manual page. 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
