Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
linux_wiki:oom_killer [2015/01/22 23:18] billdozor created OOM killer page |
linux_wiki:oom_killer [2019/05/25 23:50] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== OOM Killer ====== | ====== OOM Killer ====== | ||
| - | Description: | + | **General Information** |
| + | |||
| + | The Linux OOM (Out Of Memory) Killer is a kernel function that will automatically kill off processes if there is memory contention on a system. | ||
| + | |||
| + | **Checklist** | ||
| + | * Distro(s): Any (except for EL based kernel information at the end) | ||
| + | |||
| + | ---- | ||
| ===== OOM Function Details ===== | ===== OOM Function Details ===== | ||
| Line 27: | Line 34: | ||
| Example: | Example: | ||
| <code bash> | <code bash> | ||
| - | to do... | + | grep -i "out of memory" |
| + | Jan 15 10:05:32 dbserver01 kernel: Out of memory: Kill process 39018 (mysqld) score 441 or sacrifice child | ||
| </ | </ | ||
| ---- | ---- | ||
| - | ===== Tuning ===== | + | ===== Memory |
| Normally, when OOM is called, it is because an application has been poorly coded or configured to ask for a ridiculous amount of memory that it doesn' | Normally, when OOM is called, it is because an application has been poorly coded or configured to ask for a ridiculous amount of memory that it doesn' | ||
| Line 73: | Line 81: | ||
| The setting is from 0 to 100. | The setting is from 0 to 100. | ||
| - | * 0 = Avoid swapping for as long as possible | + | * 0 = Very aggressively avoid swapping for as long as possible |
| + | * High risk of OOM killing from memory and I/O pressure | ||
| + | * 10 = Red Hat recommended for Oracle databases | ||
| * **60 = Linux default** | * **60 = Linux default** | ||
| * 100 = Aggressively swap from memory to disk | * 100 = Aggressively swap from memory to disk | ||