[slurm-users] Temporary Stop User Submission

[Markuske, William]

Hello,

I have a badly behaving user that I need to speak with and want to temporarily disable their ability to submit jobs. I know I can change their account settings to stop them. Is there another way to set a block on a specific username that I can lift later without removing the user/account associations?

Regards,

--
Willy Markuske

HPC Systems Engineer
SDSC - Research Data Services
(619) 519-4435

wmar...@sdsc.edu

[Doug Meyer]

I always like

Sacctmgr update user where user=<userid> set grpcpus=0

[Sean Crosby]

Hi Willy,

sacctmgr modify account slurmaccount user=baduser set maxjobs=0

Sean

---

From: slurm-users <slurm-use...@lists.schedmd.com> on behalf of Markuske, William <wmar...@sdsc.edu>
Sent: Friday, 26 May 2023 09:16
To: slurm...@lists.schedmd.com <slurm...@lists.schedmd.com>
Subject: [EXT] [slurm-users] Temporary Stop User Submission

 

External email: Please exercise caution

---

[Ryan Novosielski]

I tend not to let them login. It will get their attention, and prevent them from just running their work on the login node when they discover they can’t submit. But appreciate seeing the other options.

Sent from my iPhone

> On May 25, 2023, at 19:19, Markuske, William <wmar...@sdsc.edu> wrote:
>
>  Hello,

[Markuske, William]

Sean, 

I was just about to mention this wasn't working because I had thought of something similar. I tried 'sacctmgr modify user where name=<user> set maxjobs=0' but that was still allowing the user to 'srun --pty bash'. Apparently doing it through modifying the account as you stated does work though which is odd. Just have to modify each account the user has access too.

Thanks.

Regards,

--
Willy Markuske

HPC Systems Engineer
SDSC - Research Data Services
(619) 519-4435

wmar...@sdsc.edu

[Markuske, William]

I would but unfortunately they were creating 100s of TBs of data and I need them to log in and delete it but I don't want them creating more in the meantime.

Regards,

--
Willy Markuske

HPC Systems Engineer
SDSC - Research Data Services
(619) 519-4435

wmar...@sdsc.edu

[Ole Holm Nielsen]

On 5/26/23 01:29, Doug Meyer wrote:
> I always like
>
> Sacctmgr update user where user=<userid> set grpcpus=0

This GrpCPUs group limit may perhaps affect the entire group? Anyway,
GrpCPUs is undocumented in the sacctmgr manual page, for which I opened a
bug in https://bugs.schedmd.com/show_bug.cgi?id=16832

I think Sean's suggestion of maxjobs=0 is a better choice, or perhaps set
GrpTRES=cpu=0 ?

/Ole

[Ole Holm Nielsen]

On 5/26/23 01:56, Markuske, William wrote:
> I would but unfortunately they were creating 100s of TBs of data and I
> need them to log in and delete it but I don't want them creating more in
> the meantime.

Does your filesystem have disk quotas? Using disk quotas would seem to be
a good choice to contain this problem.

/Ole

[Christopher Samuel]

On 5/25/23 4:16 pm, Markuske, William wrote:

> I have a badly behaving user that I need to speak with and want to
> temporarily disable their ability to submit jobs. I know I can change
> their account settings to stop them. Is there another way to set a block
> on a specific username that I can lift later without removing the
> user/account associations?

There are many ways to do this, our way is we set their QOS's to one
called "batchdisable" and that QOS has "MaxJobsPerUser=0" set on it.

One of the benefits of that is it's easy to see everyone who's been
blocked from submitting jobs.

All the best,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA