Difference between revisions of "Out of Memory (OOM)"
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
* <code>[[/proc/sys/vm/]]panic_on_oom</code> | * <code>[[/proc/sys/vm/]]panic_on_oom</code> | ||
* [[yarn]]: <code>[[Error Command failed with exit code 137]]</code> | * [[yarn]]: <code>[[Error Command failed with exit code 137]]</code> | ||
| − | * [[systemd-oomd]] | + | * <code>[[systemd-oomd]]</code> |
| − | + | * <code>[[pm.max_requests]]</code> | |
== See also == | == See also == | ||
Revision as of 09:25, 30 September 2022
This article is a Draft. Help us to complete it.
OOM in Docker
- Docker:
--oom-kill-disable=falseTo 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 MemoryPressureCrashLoopBackOff
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
OOM command not allowed when used memory ...
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-oomdpm.max_requests
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:
