Description of problem: In Halo replication, there are pending heals more often than not. It makes sense to give users the capability to configure it as low as 5 seconds. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/19911 (cluster/afr: Need heal-timeout to be configured as low as 5 seconds) posted (#1) for review on master by Pranith Kumar Karampuri
COMMIT: https://review.gluster.org/19911 committed in master by "Pranith Kumar Karampuri" <pkarampu> with a commit message- cluster/afr: Need heal-timeout to be configured as low as 5 seconds In Halo replication, there are pending heals more often than not. It makes sense to give users the capability to configure it as low as 5 seconds. BUG: 1569489 fixes bz#1569489 Change-Id: I451c1975827f66398b903f659c981ef3121d5376 Signed-off-by: Pranith Kumar K <pkarampu>
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-v4.1.0, please open a new bug report. glusterfs-v4.1.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://lists.gluster.org/pipermail/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/