Failure catalog · container level

Memory leak ends in an OOM kill

Container memory grows steadily until the kernel kills it at its limit.

ImpactThe container restarts and its in-flight requests fail
Can it be seen coming?Yes
RupturaCovered and tested on the lab

How to detect it

Last termination reason is OOMKilled.

Metrics and signals to watch:

Can you see it coming?

Yes Precursor: Sustained growth of memory toward the limit.

What it hits next

callers of the workload.

What to do

Raise the memory limit or fix the leak.

Sources

Where Ruptura stands

Ruptura reports this failure as the saturation failure mode, and it is measured by a pre-registered test on the lab.

Related failures

This card is part of an open catalog of 66 Kubernetes and OpenShift failures. Correct it or add one on GitHub.

See it coming instead of reading about it
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub