[slurm-users] Drain a single user's jobs

Antony Cleave antony.cleave at gmail.com
Wed Apr 1 13:22:43 UTC 2020

why not just sacctmgr modify user foo set maxjobs=0

existing running jobs will run to completion and pending jobs won't start


On Wed, 1 Apr 2020 at 10:57, Mark Dixon <mark.c.dixon at durham.ac.uk> wrote:

> Hi all,
> I'm a slurm newbie who has inherited a working slurm 16.05.10 cluster.
> I'd like to stop user foo from submitting new jobs but allow their
> existing jobs to run.
> We have several partitions, each with its own qos and MaxSubmitJobs
> typically set to some vaue. These qos are stopping a "sacctmgr update user
> foo set maxsubmitjobs=0" from doing anything useful, as per the
> documentation.
> I've tried setting up a competing qos:
>    sacctmgr add qos drain
>    sacctmgr modify qos drain set MaxSubmitJobs=0
>    sacctmgr modify qos drain set flags=OverPartQOS
>    sacctmgr modify user foo set qos=drain
> This has successfully prevented the user from submitting new jobs, but
> their existing jobs aren't running. I'm seeing the reason code
> "InvalidQOS".
> Any ideas what I should be looking at, please?
> Thanks,
> Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20200401/3b0e210d/attachment.htm>

More information about the slurm-users mailing list