Hi, 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) 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.) best wishes, Stefan > Am 21.04.2021 um 12:20 schrieb Strahil Nikolov <hunter86_bg@xxxxxxxxx>: > > You will need ro create a script to identify the pids and then protect them. > Then , you can add that script in the gluster's service file as ExecStartPost=myscript > > Another approach is to use cgroups and limit everything in the userspace. > > Best Regards, > Strahil Nikolov > > On Wed, Apr 21, 2021 at 11:52, Diego Zuccato > <diego.zuccato@xxxxxxxx> wrote: > Hello all. > > I have a somewhat undersized cluster frontend node where users (way too > often) use too much RAM. Too bad that the first process selected for > killing is the one handling the gluster mount! > > Is there a way to permanently make it "unkillable"? I already tried > altering oom_adj, but the PID changes at every boot... > > -- > 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 > ________ > > > > Community Meeting Calendar: > > Schedule - > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC > Bridge: https://meet.google.com/cpu-eiue-hvk > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/gluster-users > ________ > > > > Community Meeting Calendar: > > Schedule - > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC > Bridge: https://meet.google.com/cpu-eiue-hvk > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/gluster-users ________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
