Thanks for all the feedback, am going with Juergens MaxSubmitJobs approach.
On Thu, Oct 7, 2021 at 2:55 AM Chris Samuel wrote:
> On 6/10/21 6:21 am, byron wrote:
>
> > We have some accounts that we would like to suspend / freeze for the
> > time being that have unused hours associated with them.
On 6/10/21 6:21 am, byron wrote:
We have some accounts that we would like to suspend / freeze for the
time being that have unused hours associated with them. Is there anyway
of doing this without removing the users associated with the accounts or
zeroing their hours?
We have a QOS called "b
Hi,
I think setting MaxSubmitJobs=0 for the association should also do the
trick if you don't want to code something special in the submit.lua
script. E.g. for a single user:
sacctmgr update user set maxsubmitjobs=0
Setting MaxSubmitJobs=-1 will then release this limit.
Best regards
Jür
There are a lot of parameters controlling the resources which an account
and/or user can use. I suspect your default setup only uses a few of
them. To temporarily disable an account, you can apply a setting which is
disjoint from your normal methods.
E.g., if you normally set GrpTresMins to limi
e.g. by prohibiting submission in the submit.lua script?
Best
Marcus
Am 06.10.2021 um 15:21 schrieb byron:
We have some accounts that we would like to suspend / freeze for the time being
that have unused hours associated with them. Is there anyway of doing this
without removing the users ass
We have some accounts that we would like to suspend / freeze for the time
being that have unused hours associated with them. Is there anyway of
doing this without removing the users associated with the accounts or
zeroing their hours?
We are using slurm version 19.05.7
Thanks
