To prevent OOM from killing glusterfs process first, add ability to set oom_score_adj via command line and mount helper. This is a backport of https://bugzilla.redhat.com/show_bug.cgi?id=1336818 against 3.8 branch. Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/14605 (glusterfsd/main: Add ability to set oom_score_adj) posted (#2) for review on release-3.8 by Oleksandr Natalenko (oleksandr)
COMMIT: http://review.gluster.org/14605 committed in release-3.8 by Vijay Bellur (vbellur) ------ commit 0673af0f0c7ba64cce6b030b9194b4d35a357cd4 Author: Oleksandr Natalenko <oleksandr> Date: Tue May 17 16:45:44 2016 +0300 glusterfsd/main: Add ability to set oom_score_adj Give the administrator a possibility to set oom_score_adj for glusterfs process. Applies to Linux only. This is a backport of cb8f5e01f639cb6e8715b33bb725210cb0493887. Change-Id: Iff13c2f4cb28457871c6ebeff6130bce4a8bf543 BUG: 1341697 Signed-off-by: Oleksandr Natalenko <oleksandr> Reviewed-on: http://review.gluster.org/14399 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Jeff Darcy <jdarcy> Reviewed-on: http://review.gluster.org/14605 Reviewed-by: Kaleb KEITHLEY <kkeithle> Reviewed-by: Vijay Bellur <vbellur>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user