hard20 pts · first answer countsgokubernetesmemory
Go service OOMKilled under load
A Go service with a 1 GiB container memory limit is OOMKilled under load spikes, although its live heap is only about 450 MiB. Which change most directly helps?
Discussion 0
Join free to post in the discussion.
Related questions
- Readiness vs liveness probesSite Reliability Engineer
- A process vanished overnightSite Reliability Engineer
- CrashLoopBackOffSite Reliability Engineer
- Logs from the crashed containerSite Reliability Engineer
- PodDisruptionBudgetSite Reliability Engineer
- Exit code 137 in KubernetesSite Reliability Engineer
- HPA shows unknown CPUSite Reliability Engineer
- A pod stuck in PendingSite Reliability Engineer