It looks like I have some reading to do.
And we might be able to try this. The servers running that software are Redhat 6 and they are at 2.6.32 – and it looks like 2.6.24 is when cgroups were introduced.
Thank You for the additional idea.
What platform do you use?
On modern Linux platforms, the best way forward is to enable cgroups. This allows very precise, kernel-based management of RAM resources. It may be a better way forward than trying to work with RESERVED_SWAP.
On Feb 18, 2016, at 11:10 AM, Mary Romelfanger <mary@xxxxxxxxx
As we develop a new pipeline for a new set of instruments, we have found that we have one calibration job that is using more memory resources than we have typically had to work with before. This has me exploring new to me knobs to try to prevent
these specific jobs from taking too many resources and locking up the system.
I found and was all set to add the RESERVED_SWAP knob to my config file — because yes we have thrown both more memory and more swap space onto the test systsem, and we think it is enough to handle just about every case, but it looked like this
RESERVED_SWAP knob would be that last extra safety net (especially since the team writing the calibration software is not done yet :) ) , but I see in the v8.4 manual that a comment has been added that says "It is anticipated that this configuration variable
will no longer be used in the near future. “
Is there a new knob/better option, that I should look at, that would stop new jobs from starting if the available real system swap space dipped to low?
Thank You — Mary
Sr. Systems Software Engineer
Space Telescope Science Institute
3700 San Martin Drive
Baltimore, MD 21218
HTCondor-users mailing list
To unsubscribe, send a message to
You can also unsubscribe by visiting
The archives can be found at: