+++ This bug was initially created as a clone of Bug #1562717 +++ Description of problem: ping-event handling in halo replication is leading to marking of the bricks with high latency as down. This should be prevented for shd so that heals can happen. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Worker Ant on 2018-04-02 04:52:12 EDT --- REVIEW: https://review.gluster.org/19798 (cluster/afr: Prevent ping-event handling on shd) posted (#2) for review on master by Pranith Kumar Karampuri
REVIEW: https://review.gluster.org/19810 (cluster/afr: Prevent ping-event handling on shd) posted (#1) for review on release-3.12 by Pranith Kumar Karampuri
COMMIT: https://review.gluster.org/19810 committed in release-3.12 by "jiffin tony Thottan" <jthottan> with a commit message- cluster/afr: Prevent ping-event handling on shd On shd, we shouldn't treat any brick down based on latency, otherwise self-heal will never happen fixes: 1562723 Change-Id: Ica07fcc4fae91a6bfd9c9a670e2be464704d94b7 BUG: 1562723 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-3.12.8, please open a new bug report. glusterfs-3.12.8 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/gluster-devel/2018-April/054749.html [2] https://www.gluster.org/pipermail/gluster-users/