Failure catalog · container level

Container killed by OOM again and again

Repeated OOM kills, Kubernetes holds the container in CrashLoopBackOff.

ImpactThe workload is down most of the time
Can it be seen coming?Yes
RupturaCovered

How to detect it

CrashLoopBackOff with OOMKilled as last termination reason.

Metrics and signals to watch:

Can you see it coming?

Yes Precursor: Regular interval between kills.

What it hits next

callers of the workload.

What to do

Raise the memory limit or find the memory spike before the next kill.

Sources

Where Ruptura stands

Ruptura reports this failure as the recurrent_failure failure mode. A pre-registered lab test is not published yet.

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