When a job comes in any limit imposed by the QOS of a job will override that limit of the account.
If you want to have a specific QOS tied to an account you could make a different QOS per account and use a job-submit plugin to set it up correctly when the job comes in. Danny On 01/30/2013 01:09 PM, Lloyd Brown wrote: > Hmm. So if I have the two types of jobs associated with different QOSs, > then I can set a limit based on account and QOS, instead of account and > partition? Am I understanding correctly? > > Lloyd Brown > Systems Administrator > Fulton Supercomputing Lab > Brigham Young University > http://marylou.byu.edu > > On 01/30/2013 12:04 PM, Danny Auble wrote: >> Partitions are at the end of the hierarchy for better or worse. So you >> can think of it like this... >> >> Cluster >> Account >> User >> Partition >> >> When you create associations you are doing so in that order. So there >> is no way to make an association with a partition without a user. Just >> like there is no way to make an association for a user without an >> account. The partition part of "sacctmgr modify account where >> name=glh43 cluster=fsl partition=physics set GrpCpus=600" is invalid >> because of this schema so it is discarded. >> >> I am unaware of any way to do partition based group limits. The >> accounting limits really weren't written that way. Perhaps others have >> ways they have done this though. I am sure you aren't the only one >> wanting to do this kind of thing. >> >> You might be able to get what you want by making a QOS that matches your >> partition. That way you can get sort of what you want. >> >> Danny >> >> On 01/30/2013 10:56 AM, Lloyd Brown wrote: >>> I suspect that this is another newbie question, based on my >>> misunderstanding of something in Slurm. I hope not, but I'm guessing >>> it is. >>> >>> When we set up accounts and users for our new Slurm installation, we >>> didn't do any association with partitions, since we, in general, want >>> all users to be able to execute in all partitions. When we want to set >>> account-specific limits like GrpCPUs, we seem to be able to do that >>> using commands like this one: >>> >>> sacctmgr modify account where name=glh43 cluster=fsl set GrpCpus=600 >>> >>> This seems to successfully limit the number of running CPUs for everyone >>> under account "glh43". >>> >>> What we'd really like to do, though, is set a limit that's both >>> account-specific, and partition-specific. Something like this: >>> >>> sacctmgr modify account where name=glh43 cluster=fsl partition=physics >>> set GrpCpus=600 >>> >>> But whenever I try it, I get a "Nothing Modified" output. >>> >>> So, is this possible to set an account-specific and partition-specific >>> limit? Do I need to do something different with my account setup? We >>> don't want to limit the users in "glh43" account to the "physics" >>> partition or anything; we just want to limit the number of running >>> processors by the users in "glh43" in the "physics" partition, >>> independent of the limits for "glh43" in any other partition. >>> >>> Does that make sense? >>> >>> Thanks, >>>
