Failure catalog · container level

Container runs out of process IDs

fork fails, the process cannot start threads or children.

ImpactRequests fail, the container may hang
Can it be seen coming?Yes
RupturaPlanned

How to detect it

Process count near the PID limit.

Metrics and signals to watch:

Can you see it coming?

Yes Precursor: Thread or process count growing steadily.

What it hits next

callers of the workload, other pods of the node.

What to do

Fix the thread leak or raise the PID limit.

Sources

Where Ruptura stands

This failure is on the Ruptura roadmap. It is not reported 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