-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/03/14 04:53, Lyn Gerner wrote:
> Have you also set AccountingStorageEnforce appropriately, as > described here: http://slurm.schedmd.com/resource_limits.html ? We've had the association one from the start (we rely on hard limits for CPU time for projects - i.e. accounts) so my first go with association based limits should have worked. However, I didn't when I sent that email for the QoS based limits though I fixed it shortly afterwards. I have a suspicion though that in the short window between me sending that email and adding qos as an enforcement a number of the problem users jobs finished, taking them below the 192 job cut off. :-/ My next task is to figure out how to implement the equivalent of Maui/Moab's MAXIJOB such that any more than (say) 5 waiting jobs of a user get marked as QOSResourceLimit, and then patch our local showq to treat those as "blocked" and hide them from other users. cheers, 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMVBa8ACgkQO2KABBYQAh/rRACgiGzYFXGkXtgWEkhAvDZqgkRN 6jAAoIiWdQDbRLsuGo7ztgMDv+fceakb =gpfc -----END PGP SIGNATURE-----
