Difference between revisions of "Out of Memory (OOM)"
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
== OOM Linux kernel logs == | == OOM Linux kernel logs == | ||
− | Jan 26 04:40:29 SERVER_NAME kernel: [[runc]]:[2:INIT] invoked [[oom-killer]]: [[gfp_mask]]=0x14000c0(GFP_KERNEL), nodemask=(null), order=0, oom_score_adj=0 | + | Jan 26 04:40:29 SERVER_NAME kernel: [[runc]]:[2:INIT] invoked [[oom-killer]]: [[gfp_mask]]=0x14000c0(GFP_KERNEL), nodemask=(null), order=0, [[oom_score_adj]]=0 |
Jan 26 04:40:29 SERVER_NAME kernel: [[oom_reaper]]: reaped process 22572 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB | Jan 26 04:40:29 SERVER_NAME kernel: [[oom_reaper]]: reaped process 22572 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB |
Revision as of 17:26, 28 October 2022
OOM in Docker
- Docker:
--oom-kill-disable=false
To enable or disable OOM Killer for the container.
Use docker inspect CONTANINER_NAME | grep OOM
to show options. For example:
docker inspect grafana | grep -i OOM "OOMKilled": false, "OomScoreAdj": 0, "OomKillDisable": false,
Kubernetes
Pod The node had condition: [MemoryPressure].
kubectl describe nodes | grep MemoryPressure
CrashLoopBackOff
OOM Linux kernel logs
Jan 26 04:40:29 SERVER_NAME kernel: runc:[2:INIT] invoked oom-killer: gfp_mask=0x14000c0(GFP_KERNEL), nodemask=(null), order=0, oom_score_adj=0
Jan 26 04:40:29 SERVER_NAME kernel: oom_reaper: reaped process 22572 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Redis
Related terms
Java.lang.OutOfMemoryError: Java heap space
- Out of space
/proc/sys/vm/panic_on_oom
- yarn:
Error Command failed with exit code 137
systemd-oomd
pm.max_requests
EarlyOOM
See also
- Memory: memory pages, RAM, virsh Memory Commands, OOM, meminfo,
vmstat
, NAND, DDR,lsmem
,/dev/shm
,/proc/meminfo
,sar -r
, IOMMU,pmem
, Memory management, Garbage collector, THP, Linux Huge Page TLB - OOM, EarlyOOM, OOM Killer, MemoryPressure (K8s),
systemd-oomd, OOMKilled, oom-killer, memcpy
,sar -r
,Exit code: 137
, Killed process - ENOMEM
Advertising: