Re: [HTCondor-users] Memory accounting issue with cgroups

[Marco van Zwetselaar <zwets@xxxxxxxxxx>]

Hoi Jan,

Great! This appears to be resolved in 10.6. Just tried with 
10.6.0-0.647603_amd64.deb, and all goes well. Reported memory first goes 
up by 1GB/5mn but then stops just below the limit.

I can see the cgroup's memory.max is now being set, but not its 
memory.high (whereas docs suggested it would be at 90% of max). This had 
me worried that my job would be kicked out as soon as it went over, but 
clearly that isn't the case.

I guess my mental picture of memory.high as a yellow card, and 
memory.max as the red card was incorrect. It's more like rugby: the 
referee's stare is enough. :-)

On a side note to the Condor devs: my config has 'DISABLE_SWAP_FOR_JOB = 
true'. Shouldn't that translate to 'memory.swap.max = 0' on the cgroup 
(currently shows "max")?

Thanks again,
Marco


On 19/05/2023 10:37, Jan van Eldik wrote:
> Hallo Marco,
>
> Could this be the issue addressed in 
> https://github.com/htcondor/htcondor/commit/3c1b39bf5607d7485aa36e90ab8f6de6f99baeb0
>
> Release condor-10.6.0-0.644330.el9.x86_64 includes this, and we have not
> observed any cgroups-v2 related crashes on our EL9 servers since we 
> deployed it a few weeks ago.
>
>
> ÂÂ hope this helps, groeten, Jan
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx 
> with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/