<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">Bill - thank you for the code. </span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">For the record, our queues explicitly block any requests greater
than what the queue allows - MaxMemPerNode = 64 GiB's.</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">If there are any other ideas, feel free to comment.</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">Sandor</span></div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> slurm-users <slurm-users-bounces@lists.schedmd.com> on behalf of Bill <bill@princeton.edu><br>
<b>Sent:</b> Thursday, December 8, 2022 7:52 AM<br>
<b>To:</b> slurm-users@lists.schedmd.com <slurm-users@lists.schedmd.com><br>
<b>Subject:</b> Re: [slurm-users] srun --mem issue</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.<br>
<br>
If you use a job_submit.lua script just add<br>
<br>
if job_desc.pn_min_memory == 0 or job_desc.min_mem_per_cpu == 0 then<br>
log_info("slurm_job_submit: job from uid %d invalid memory <br>
request MaxMemPerNode", job_desc.user_id)<br>
return 2044 -- signal ESLURM_INVALID_TASK_MEMORY<br>
end<br>
<br>
<br>
Bill<br>
<br>
On 12/7/22 12:03 PM, Felho, Sandor wrote:<br>
> TransUnion is running a ten-node site using slurm with multiple queues. <br>
> We have an issue with --mem parameter. The is one user who has read the <br>
> slurm manual and found the --mem=0. This is giving the maximum memory on <br>
> the node (500 GiB's) for the single job. How can I block a --mem=0 request?<br>
> <br>
> We are running:<br>
> <br>
> * OS: RHEL 7<br>
> * cgroups version 1<br>
> * slurm: 19.05<br>
> <br>
> Thank you,<br>
> <br>
> *Sandor Felho *<br>
> <br>
> Sr Consultant, Data Science & Analytics<br>
> <br>
> <br>
<br>
</div>
</span></font></div>
</body>
</html>