Why a Java pod gets OOMKilled in Kubernetes with a half-empty heap
Comments
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Summary
A Java pod can be OOMKilled while its heap is only half full, because the container memory limit also has to cover metaspace, thread stacks, the code cache and direct buffers.