Re: OOM kills gluster process

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Il 21/04/21 12:20, Strahil Nikolov ha scritto:

Tks for answering.

> 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
Well, using pidof or the runfile contents it should be doable...
Probably the runfile is the best option. I'll try it.

> Another approach is to use cgroups and limit everything in the userspace.
Tried that, but have had to revert the change: SLURM is propagating
ulimits to the nodes... Going to ask in the SLURM list ...

-- 
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




[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux