OOMKilled: Why Your Container Died With Clean Metrics
Exit code 137, a memory graph that looks perfectly healthy, and no application error. Here is why your monitoring missed it and how to find the real number.
| Component | In your heap metric | Counted by the cgroup |
|---|---|---|
| Managed heap | yes | yes |
| JVM metaspace and code cache | no | yes |
| Thread stacks, 1MB each | no | yes |
| Direct and off heap buffers | no | yes |
| Native library allocations | no | yes |
| Memory mapped files | no | yes |
| Page cache from reading and writing files | no | yes |
| Kernel socket buffers | no | yes |
Related reading: The latest Tag That Deployed Yesterday's Build explores a connected angle.
Related reading: x509: certificate signed by unknown authority explores a connected angle.
Related reading: ImagePullBackOff vs ErrImagePull: What Each One Means explores a connected angle.
Published on debugly.dev by Rohit Bhadani | Founder of Krova Cloud
