Hello everyone, I came across a weird behavior and was wondering if this is a bug, oversight, or intended?
It appears that Slurm does not set memory.limit_in_bytes at the task level, but it does set it at the step level and above. Observe: $ grep memory /proc/$$/cgroup 10:memory:/slurm/uid_2001/job_304876/step_0/task_0 $ cd /sys/fs/cgroup/memory/slurm/uid_2001/job_304876/step_0/task_0 $ cat memory.limit_in_bytes 9223372036854771712 <--- basically unlimited But lets check the parent: $ cat ../memory.limit_in_bytes 33554432000 <-- set properly to around 32 GB, see below $ scontrol show job 304876 | grep mem= TRES=cpu=8,mem=*32000M*,node=1,billing=8 Now, it does appear that the task is still limited to the step's memory limit given the hierarchical nature of cgroups, but I just wanted to mention this anyway and see if anyone had any thoughts. Thanks, __________________________________________________ *Jacob D. Chappell, CSM* Research Computing | Research Computing Infrastructure Information Technology Services | University of Kentucky jacob.chapp...@uky.edu
