MATCHES FOR “OOMKILLED”
sorted by similarityincident memory · stored Jul 02 · source OPS-377
payments-api OOMKilled after JVM upgrade
SYMPTOMS
Pods in CrashLoopBackOff, last state OOMKilled (exit 137), memory climbs past the limit within a minute of start.
ROOT CAUSE
New JVM base image sizes heap from container memory differently; 256Mi limit no longer fits heap plus metaspace.
WHAT FIXED IT
Raised memory limit to 512Mi and set -XX:MaxRAMPercentage=70. Verified 30 minutes without restarts.
WHAT DID NOT WORK
Restarting the deployment. Rolling back only the app image.
RECALLED IN
- OPS-412 · payments-api CrashLoopingopen
- OPS-395 · ledger-api restartsfixed
- CU-8702 · billing-worker OOMfixed
STORAGE
- Record
- Postgres · incidents
- Embedding
- Qdrant · incidents_v1
- Match score
- 0.94