Incident Library

API · MCP 한국어

API and MCP kubegap Corrections and proposals

Incident Library

API · MCP 한국어

Component

Container CPU limit

컨테이너 CPU 한도 · cpu-limit

5 cases · 2020 to 2026

Root cause Software defect3 Capacity exhaustion2

Contributing factor Monitoring blind spot3 Unpatched known bug2 Unverified assumption1 Unreviewed defaults1 Unknown limit1

Symptom CPU throttling4 High latency4 High error rate1 Intermittent connection failures1

Organisation Buffer1 Hyperconnect1 Kevin1 Omio1 Temporal1

Cases, by severity

IL-0181 A traffic spike from an external community post pushed product API pods into CPU throttling under a 1-core limit, and an e-commerce product page slowed down while every pod stayed RunningKevin · 2026
Root cause Capacity exhaustion
IL-0028 Temporal History service latency rose because its pods were CPU-throttled while CPU usage read below 60 percentTemporal · 2023
Root cause Capacity exhaustion
IL-0175 Lowering a JVM pod's CPU request from 2 to 1 pushed memory past the 90% alert because the JVM treats a cgroup v1 cpu.shares value of exactly 1024 as unset and sized Reactor Netty threads from the node's 36 CPUs

View on the graph

No resource requests or limits1

Intermittent timeouts1

Memory pressure1

Probe failures1

Hyperconnect · 2022

Root cause Software defect

IL-0029 Slow user-facing services from CPU throttling on containers that used far less CPU than their limitBuffer · 2020

Root cause Software defect

IL-0012 CPU limits and an unpatched kernel CFS quota bug throttled multi-threaded services into stalls, failed health checks and timeoutsOmio · 2020

Root cause Software defect