Node runs out of inodes
Free inodes fall to zero while space remains.
ImpactFiles cannot be created, containers fail to start
Can it be seen coming?Yes
RupturaNot covered yet
How to detect it
Free inodes below a threshold.
Metrics and signals to watch:
node_filesystem_files_free
Can you see it coming?
Yes Precursor: Steady fall of free inodes.
What it hits next
every pod of the node.
What to do
Remove the many small files, often logs or caches.
Sources
- node-exporter NodeFilesystemFilesFillingUp
- node-exporter NodeFilesystemAlmostOutOfFiles
Where Ruptura stands
Ruptura does not cover this failure yet. The card is here so you know it exists and how to detect it.
Related failures
- Node not ready
- Node flaps between Ready and NotReady
- Node under memory pressure
- Node under disk pressure
- Node under PID pressure
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
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