Set a container memory limit per server and warn when memory is overcommitted

Open
#213 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, typescript

Research direction

Start by locating the server container configuration and the existing resource_usage and watchdog code mentioned in the issue. Trace how Java heap and Bedrock memory settings are stored and passed to containers, then identify the create, edit, and dashboard flows that show allocated memory. Done means per-container limits and overcommit warnings work across those flows, and an OOM-killed container is reported as out of memory.

Written by the indexing model from the issue text.

Description

enhancement

MEMORY only sets the Java heap. Server containers have no mem_limit, so a server set to 4G really uses about 4.5-5G once JVM overhead is counted, and several of them can push the host into the kernel's OOM killer. That can take out an unrelated server or Isopod itself, which looks like random restarts.

Fix

  • Give each Java server container a memory limit of heap plus headroom (e.g. heap + 25%, at least 512M). Bedrock gets a limit from its own setting.
  • When the memory given to all servers adds up to more than the host has, warn on create, on edit, and on the dashboard. resource_usage already totals allocated memory.
  • When a container hits its limit, report it as out of memory (the watchdog already reads OOMKilled).

Acceptance

  • One runaway server can only kill itself.
  • Overcommitting memory shows a warning before you save.
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
13h 12m
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.