-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks,
The Slurm 2.6.5 sacctmgr manual page says for MaxJobs in associations: MaxJobs=<max jobs> Maximum number of jobs each user is allowed to run at one time in this association. This is overridden if set directly on a user. Default is the cluster�s limit. To clear a previously set value use the modify command with a new value of -1. I've just tried setting it with: # sacctmgr modify account set maxjobs=192 where cluster=barcoo and account=foo and I can see the expected values when I do: # sacctmgr show assoc where cluster=barcoo account=foo but it doesn't appear to have any effect. I've tried restarting slurmctld on the node just in case. FWIW we also have per account GrpCPUs set too (at 840) to limit the number of cores a project can use, but I would expect Slurm to apply both limits. Is there something I'm missing, or is this a bug? All the best, Chris - -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMT0+AACgkQO2KABBYQAh++kwCfec8qdNK56yilOvmMQoZjzJ8H Rj0An1HU11M2x9sk2XBcIRoEgTyR6W0i =Apk+ -----END PGP SIGNATURE-----
