+++ This bug was initially created as a clone of Bug #1352019 +++ Description of problem: Throttling is feature by itself which any component can consume, hence it more suitable to be part of libglusterfs than to be of bitrot. Version-Release number of selected component (if applicable): mainline How reproducible: NA Steps to Reproduce: NA Actual results: Throttling code is part of bitrot Expected results: Throttling code should be part of libglusterfs
REVIEW: http://review.gluster.org/14944 (features/bitrot: Move throttling code to libglusterfs) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/14944 committed in release-3.7 by Jeff Darcy (jdarcy) ------ commit 2526f9d3ddc3e7f62828ac4289001b22638ae42a Author: Kotresh HR <khiremat> Date: Fri Jul 1 15:54:07 2016 +0530 features/bitrot: Move throttling code to libglusterfs Backport of http://review.gluster.org/14846 Since throttling is a separate feature by itself, move throttling code to libglusterfs. Change-Id: If9b99885ceb46e5b1865a4af18b2a2caecf59972 BUG: 1357514 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/14944 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Jeff Darcy <jdarcy>
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.7.14, please open a new bug report. glusterfs-3.7.14 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] https://www.gluster.org/pipermail/gluster-devel/2016-August/050319.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user