Not required, but useful #6

New issue

Open

opened 2026-05-25 13:03:57 +00:00 by ezozbek36 · 2 comments

ezozbek36 commented

2026-05-25 13:03:57 +00:00

Owner

https://dev.to/rrampage/surviving-the-linux-oom-killer-2ki9
https://unix.stackexchange.com/questions/58872/how-to-set-oom-killer-adjustments-for-daemons-permanently

https://dev.to/rrampage/surviving-the-linux-oom-killer-2ki9 https://unix.stackexchange.com/questions/58872/how-to-set-oom-killer-adjustments-for-daemons-permanently

ezozbek36 commented

2026-05-25 13:04:30 +00:00

Author

Owner

We should prevent killing relago services in oom conditions

ezozbek36 commented

2026-05-25 13:05:12 +00:00

Author

Owner

useful kernel memory tunings

https://www.kernel.org/doc/Documentation/sysctl/vm.txt

oom_dump_tasks

Enables a system-wide task dump (excluding kernel threads) to be produced
when the kernel performs an OOM-killing and includes such information as
pid, uid, tgid, vm size, rss, pgtables_bytes, swapents, oom_score_adj
score, and name. This is helpful to determine why the OOM killer was
invoked, to identify the rogue task that caused it, and to determine why
the OOM killer chose the task it did to kill.

If this is set to zero, this information is suppressed. On very
large systems with thousands of tasks it may not be feasible to dump
the memory state information for each one. Such systems should not
be forced to incur a performance penalty in OOM conditions when the
information may not be desired.

If this is set to non-zero, this information is shown whenever the
OOM killer actually kills a memory-hogging task.

The default value is 1 (enabled).

==============================================================

oom_kill_allocating_task

This enables or disables killing the OOM-triggering task in
out-of-memory situations.

If this is set to zero, the OOM killer will scan through the entire
tasklist and select a task based on heuristics to kill. This normally
selects a rogue memory-hogging task that frees up a large amount of
memory when killed.

If this is set to non-zero, the OOM killer simply kills the task that
triggered the out-of-memory condition. This avoids the expensive
tasklist scan.

If panic_on_oom is selected, it takes precedence over whatever value
is used in oom_kill_allocating_task.

The default value is 0.

useful kernel memory tunings https://www.kernel.org/doc/Documentation/sysctl/vm.txt > > oom_dump_tasks > > Enables a system-wide task dump (excluding kernel threads) to be produced > when the kernel performs an OOM-killing and includes such information as > pid, uid, tgid, vm size, rss, pgtables_bytes, swapents, oom_score_adj > score, and name. This is helpful to determine why the OOM killer was > invoked, to identify the rogue task that caused it, and to determine why > the OOM killer chose the task it did to kill. > > If this is set to zero, this information is suppressed. On very > large systems with thousands of tasks it may not be feasible to dump > the memory state information for each one. Such systems should not > be forced to incur a performance penalty in OOM conditions when the > information may not be desired. > > If this is set to non-zero, this information is shown whenever the > OOM killer actually kills a memory-hogging task. > > The default value is 1 (enabled). > > ============================================================== > > oom_kill_allocating_task > > This enables or disables killing the OOM-triggering task in > out-of-memory situations. > > If this is set to zero, the OOM killer will scan through the entire > tasklist and select a task based on heuristics to kill. This normally > selects a rogue memory-hogging task that frees up a large amount of > memory when killed. > > If this is set to non-zero, the OOM killer simply kills the task that > triggered the out-of-memory condition. This avoids the expensive > tasklist scan. > > If panic_on_oom is selected, it takes precedence over whatever value > is used in oom_kill_allocating_task. > > The default value is 0.