Resource Exhaustion
159 incident problems that show up as “Resource Exhaustion”.
먼저 읽을 가이드
추천 문제
All problems (159)
LINUX-090Systemd cgroup memory limit kills the helper process and the main service logs look unrelatedThe application seems to fail in an unrelated code path, but the hidden cause is a helper process being OOM-killed inside the unit's cgroup budget.LinuxAdvanced18 minProLINUX-080XFS project quota silently blocks writes inside the container content pathThe filesystem still has free space, but one workload starts failing writes because a project quota limit was reached on the specific content subtree it uses.LinuxAdvanced18 minProSECURITY-336Containment revokes general egress while one evidence collection or telemetry upload endpoint was still needed for the investigation during a failover rehearsalThe isolation step works and responders lose the path that would have made the incident explainable. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.SecurityAdvanced19 minProK8S-073Ephemeral-storage eviction startsThe nodes still have CPU and memory, but pods get evicted because local ephemeral storage fills when retry-heavy request logging lands in emptyDir volumes.KubernetesAdvanced19 minProCICD-072GitHub Actions matrix deploy runs twice in productionThe workflow looks serialized, but two production deploys still overlap because the concurrency group ignores environment or region and only keys on the branch name.CI/CDAdvanced19 minProLINUX-081OverlayFS upperdir fills the root filesystem while the underlying data volume still looks emptyContainer workloads write successfully for a while, but the host runs out of space because the upper layer resides on root and not on the large data device operators are watching.LinuxAdvanced19 minProSECURITY-589A SIEM parser update normalizes timestampsA SIEM parser update normalizes timestamps focuses on Incident Response Operations and asks the reader to isolate Resource Exhaustion in Azure. 실무에서는 resource-exhaustion 경보만 보는 대신 자산 범위, 권한 변경 이력, 인증서나 정책 만료, 우회 경로 존재 여부를 같이 확인해야 대응 우선순위를 제대로 잡을 수 있습니다. Incident Response 관점의 점...SecurityIntermediate20 minProK8S-095Pod anti-affinity keeps a restore blockedCapacity exists, but strict anti-affinity rules stop recovery because the surviving node already runs the same workload family.KubernetesAdvanced20 minProSECURITY-649A SIEM parser update normalizes timestampsA SIEM parser update normalizes timestamps focuses on Incident Response Operations and asks the reader to isolate Resource Exhaustion in Azure. 실무에서는 resource-exhaustion 경보만 보는 대신 자산 범위, 권한 변경 이력, 인증서나 정책 만료, 우회 경로 존재 여부를 같이 확인해야 대응 우선순위를 제대로 잡을 수 있습니다. Incident Response 관점의 점...SecurityIntermediate21 minProLINUX-065LVM snapshot reaches 100 percent and the application filesystem stallsThe origin volume still has free space, but writes slow or freeze because the snapshot copy-on-write area filled and the backup workflow never released it.LinuxAdvanced22 minProK8S-088StatefulSet ordinal reuses a stale PVC and replays old node identity into the quorum clusterThe pod comes up, but the distributed system behaves incorrectly because the restored ordinal is carrying a PVC from a previous logical member.KubernetesAdvanced23 minProLINUX-035PAM limits are raised but the systemd service still hits too many open filesInteractive shells inherit the new limit correctly, but the daemon still fails under load because its service-level limit remains unchanged.LinuxAdvanced25 minProK8S-059PriorityClass protects system pods but starves customer workloads during node pressureThe cluster keeps critical control components alive as intended, but the chosen priority and preemption policy leave business workloads permanently unschedulable.KubernetesAdvanced25 minProLINUX-026Swap activity stays high after memory spike is goneSwap activity stays high (Timeouts and Latency) is a hands-on troubleshooting drill. The incident is over, but swap churn remains elevated and keeps latency unpredictable for the rest of the day. Linux Service Operations needs to be checked by narrowing scope, recent change, a...LinuxAdvanced25 minProLINUX-058XFS log recovery loop continues after an unclean volume detachThe block device is back online, but the filesystem still refuses to mount cleanly because the recovery path never completed and the operator keeps retrying the same mount blindly.LinuxAdvanced25 minProCICD-054Buildx multi-arch pipeline failsThe image builds successfully for one architecture, but the overall publish stage fails when temporary layers and cache exports exceed the runner disk budget.CI/CDAdvanced26 minProLINUX-023Ephemeral disk pressure kills cache but not the root causeEphemeral disk pressure kills cache but not the root cause is a hands-on troubleshooting drill. Cleaning temp files buys time, but write amplification from another process quickly recreates the same disk pressure. Linux Service Operations needs to be checked by narrowing scope...LinuxAdvanced26 minProSECURITY-1009A SIEM parser update normalizes timestampsA SIEM parser update normalizes timestamps focuses on Incident Response Operations and asks the reader to isolate Resource Exhaustion in Azure. 실무에서는 resource-exhaustion 경보만 보는 대신 자산 범위, 권한 변경 이력, 인증서나 정책 만료, 우회 경로 존재 여부를 같이 확인해야 대응 우선순위를 제대로 잡을 수 있습니다. Incident Response 관점의 점...SecurityIntermediate27 minProLINUX-040Overlay mount reports no space left on device while df still shows free blocksContainer creation fails with a storage error even though normal disk and inode checks look healthy, pointing to overlay, mount, or lower-level storage limits rather than a simple full disk.LinuxAdvanced27 minProK8S-054Volume attach succeeds but the pod never mountsThe control plane reports the volume attachment as healthy, yet the pod stays stuck on a subset of nodes because the node-side plugin is not present everywhere.KubernetesAdvanced27 minPro