Add RAM sentinel daemon for OOM prevention - #160
Open
idelcano wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📌 References
Issue: https://app.clickup.com/t/4528615/869e36g3p
📝 Implementation
Adds
ram_sentinel.py, a daemon that monitors available RAM and stopsMonit-managed services when memory drops critically low, then restores
them once RAM recovers. Configured per-environment via systemd ExecStart
flags — no code changes needed between servers.
Key design decisions:
kill(SIGKILL via Monit PID, for Java/Tomcat)and
stop(clean monit stop, for Docker/Postgres)is resumed on daemon restart
--dry-runmode reads RAM and PIDs for real but skips all destructivecommands
How to install
ram_sentinel.pyto/usr/local/bin/ram_sentinel.pyforce an emergency cycle and verify tier names and PID resolution:
python3 /usr/local/bin/ram_sentinel.py
--emergency-trigger <above_current_available_MB to test>
--safe-recovery <target_MB>
--tier kill:<monit_name>
--dry-run
[DRY-RUN] would...foreach action
.servicefile for the server to/etc/systemd/system/ram-sentinel.servicesystemctl daemon-reload && systemctl enable --now ram-sentinel
journalctl -u ram-sentinel -f