[Gluster-users] [EXT] OOM kills gluster process
Diego Zuccato
diego.zuccato at unibo.it
Thu Apr 22 09:32:29 UTC 2021
Il 21/04/21 13:04, Stefan Solbrig ha scritto:
Tks for answering.
> You could also consider disabling overcommitting memory: /etc/sysctl.d/<whatever>:
> vm.overcommit_memory = 2
> vm.overcommit_ratio = 100
> (See https://www.kernel.org/doc/Documentation/vm/overcommit-accounting)
Interesting idea, but a bit of swapping is not too bad.
> This way, If users allocate too much memory, they get an error upon allocation.
> This should limit the cases where the oom killer needs to take action.
> however, it has other side effects, like killing user programs that overcommit
> by default. (Or user programs that fork() a lot.)
Actually the fork()-intensive programs are the ones that most likely are
behaving badly... I'll have to dig deeper.
--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
More information about the Gluster-users
mailing list