[slurm-users] srun --mem issue

Loris Bennett loris.bennett at fu-berlin.de
Thu Dec 8 08:33:19 UTC 2022


Moshe Mergy <moshe.mergy at weizmann.ac.il> writes:

> Hi Sandor
>
> I personnaly block "--mem=0" requests in file job_submit.lua (slurm 20.02):
>
>   if (job_desc.min_mem_per_node == 0  or  job_desc.min_mem_per_cpu == 0) then
>         slurm.log_info("%s: ERROR: unlimited memory requested", log_prefix) 
>         slurm.log_info("%s: ERROR: job %s from user %s rejected because of an invalid (unlimited) memory request.", log_prefix, job_desc.name, job_desc.user_name) 
>         slurm.log_user("Job rejected because of an invalid memory request.") 
>         return slurm.ERROR
>    end

What happens if somebody explicitly requests all the memory, so in
Sandor's case --mem=500G ?

> Maybe there is a better or nicer solution...
>
> All the best
> Moshe
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> From: slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of Felho, Sandor <Sandor.Felho at transunion.com>
> Sent: Wednesday, December 7, 2022 7:03 PM
> To: slurm-users at lists.schedmd.com
> Subject: [slurm-users] srun --mem issue 
>  
> TransUnion is running a ten-node site using slurm with multiple queues. We have an issue with --mem parameter. The is one user who has read the slurm manual and found the
> --mem=0. This is giving the maximum memory on the node (500 GiB's) for the single job. How can I block a --mem=0 request?
>
> We are running:
>
> * OS: RHEL 7
> * cgroups version 1
> * slurm: 19.05
>
> Thank you,
>
> Sandor Felho 
>
> Sr Consultant, Data Science & Analytics 
>
-- 
Dr. Loris Bennett (Herr/Mr)
ZEDAT, Freie Universität Berlin



More information about the slurm-users mailing list