Description of problem: If the number of background heals increase then the mount can die because of OOM killers. Number of background heals need to be throttled. 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/11471 (cluster/ec: Add throttling in background healing) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/11472 (cluster/ec: Remove dead code) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/11473 (cluster/ec: Make background healing optional behavior) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/11495 (libglusterfs: Use GF_CALLOC/GF_FREE instead of CALLOC/FREE) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/11472 committed in master by Vijay Bellur (vbellur) ------ commit c66026b9bf521172f49ce36a5a7b94fae1bbf267 Author: Pranith Kumar K <pkarampu> Date: Tue Jun 30 22:09:57 2015 +0530 cluster/ec: Remove dead code Change-Id: I99d7a038f29cebe823e17a8dda40d335441185bc BUG: 1237381 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/11472 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Xavier Hernandez <xhernandez> Tested-by: NetBSD Build System <jenkins.org>
COMMIT: http://review.gluster.org/11471 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit fb20db2078dd7fe1a202f8c0c6f8bd7ecc7ff875 Author: Pranith Kumar K <pkarampu> Date: Tue Jun 30 18:45:36 2015 +0530 cluster/ec: Add throttling in background healing - 8 parallel heals can happen. - 128 heals will wait for their turn - Heals will be rejected if 128 heals are already waiting. Change-Id: I2e99bf064db7bce71838ed9901a59ffd565ac390 BUG: 1237381 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/11471 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Xavier Hernandez <xhernandez> Tested-by: NetBSD Build System <jenkins.org>
REVIEW: http://review.gluster.org/11473 (cluster/ec: Make background healing optional behavior) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/11495 committed in master by Vijay Bellur (vbellur) ------ commit e7f2547f89dbcd90cdb3714f63620a36bdc2ef3a Author: Pranith Kumar K <pkarampu> Date: Wed Jul 1 22:32:44 2015 +0530 libglusterfs: Use GF_CALLOC/GF_FREE instead of CALLOC/FREE - Also removed numbers for the types as the string form of type is printed in statedump now, so the numbers are not needed anymore. Change-Id: I6e8c15a1dc8cb6187842f96f1d46ec0f26a602b4 BUG: 1237381 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/11495 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/11473 (cluster/ec: Make background healing optional behavior) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/11473 (cluster/ec: Make background healing optional behavior) posted (#4) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/11473 committed in master by Xavier Hernandez (xhernandez) ------ commit c6742adc98a9747f5e16c242aaddc28ea991ec5a Author: Pranith Kumar K <pkarampu> Date: Tue Jun 30 23:01:36 2015 +0530 cluster/ec: Make background healing optional behavior Provide options to control number of active background heal count and qlen. Change-Id: Idc2419219d881f47e7d2e9bbc1dcdd999b372033 BUG: 1237381 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/11473 Reviewed-by: Xavier Hernandez <xhernandez> Tested-by: Gluster Build System <jenkins.com>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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