Resource Exhaustion
159 incident problems that show up as “Resource Exhaustion”.
먼저 읽을 가이드
추천 문제
All problems (159)
LINUX-132A tmpfs runs out of inodes long before bytes, and the application reports no-space-left while monitoring still shows free memoryCapacity alarms focus on memory size, but the real exhaustion point is object count.LinuxIntermediate15 minProLINUX-134Coredumps are enabled, but the external coredump partition is full so every crash report silently disappearsDevelopers expect postmortem artifacts, yet the configured storage target has no remaining capacity.LinuxIntermediate15 minProK8S-132A cloned PersistentVolume inherits the wrong reclaim policy and deleting the test claim removes the only remaining copyThe clone appears safe for testing, but one lifecycle flag still ties cleanup to the underlying data fate.KubernetesIntermediate16 minProK8S-147A Deployment uses maxUnavailable zero, but node pressure evicts old pods anyway and the rollout briefly drops below the intended floorThe rollout strategy is conservative, yet external eviction pressure overrides the update assumptions.KubernetesIntermediate16 minProLINUX-375A log rotation policy is correct while a filebeat or rsyslog harvester keeps the deleted descriptor open and disk usage never falls during a staged decommissionThe rotated files are gone from the directory and still present on disk. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.LinuxIntermediate16 minProLINUX-168A telemetry agent writes checkpoints to the small root disk instead of the intended data mount during a failover rehearsalLogs keep flowing while state files quietly consume the partition the system needs most. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.LinuxIntermediate16 minProK8S-139HPA scale-down stabilization holds extra replicas during a rollout, and the Deployment budget never frees enough capacity for the next revisionNothing is obviously broken, but overlapping controller safety windows create a deadlock on available resources.KubernetesIntermediate16 minProK8S-198A conservative rollout budget still loses availability when cluster pressure starts evicting old pods during a failover rehearsalDeployment math is correct, yet platform pressure changes the effective availability story. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.KubernetesIntermediate17 minProK8S-234A CSI expansion updates the block device size while the filesystem inside the pod still reports the old geometry during a failover rehearsalThe storage control plane moved forward and the in-pod view of usable capacity did not. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.KubernetesIntermediate17 minProK8S-336A custom metric adapter reports current values while the HPA history window is still full of high samples and scale-down never happens when expected during a failover rehearsalThe metric is honest now, but the autoscaling controller still reasons over a past you forgot to inspect. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.KubernetesIntermediate17 minProLINUX-228A journal vacuum policy frees one filesystem while a coredump directory on another keeps growing unchecked during a failover rehearsalLogs look healthy and the diagnostic path that really consumes space was outside the cleanup policy. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.LinuxIntermediate17 minProLINUX-312A journald retention policy frees local logs while remote-forward queue spillover still fills the spool filesystem during collector outages during a failover rehearsalLog retention seems tuned and the buffering path for remote resilience is where storage actually disappears. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.LinuxIntermediate17 minProK8S-127A very generous startup probe masks a crash loop during rollout, and autoscaling expands the broken ReplicaSet before anyone noticesThe app never becomes truly healthy, but the rollout budget is consumed on pods that are still within the startup grace window.KubernetesIntermediate17 minProLINUX-495A log rotation policy is correct (Resource Exhaustion)A log rotation policy is correct (Resource Exhaustion) focuses on linux-performance-and-observability and asks the reader to isolate Resource Exhaustion. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을...LinuxIntermediate18 minProK8S-240An HPA reads CPU from the main container while the injected sidecar consumes most of the real workload headroom during a failover rehearsalThe autoscaler sees one process and the pod's real bottleneck lives somewhere else. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.KubernetesIntermediate18 minProLINUX-494A log rotation policy is correct (Resource Exhaustion)A log rotation policy is correct (Resource Exhaustion) focuses on linux-performance-and-observability and asks the reader to isolate Resource Exhaustion. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을...LinuxIntermediate19 minProLINUX-554A log rotation policy is correct (Resource Exhaustion)A log rotation policy is correct (Resource Exhaustion) focuses on linux-performance-and-observability and asks the reader to isolate Resource Exhaustion. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을...LinuxIntermediate20 minProLINUX-611A log rotation policy is correct (Resource Exhaustion)A log rotation policy is correct (Resource Exhaustion) focuses on linux-performance-and-observability and asks the reader to isolate Resource Exhaustion. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을...LinuxIntermediate20 minProK8S-040Node eviction startsApplication storage looks healthy on the persistent volume, but a temporary working directory on the node root filesystem silently fills and triggers eviction pressure.KubernetesIntermediate24 minPro