Description of problem: This RFE is to track the changes required in the AFR component to generate the events to be consumed by the eventing framework.
REVIEW: http://review.gluster.org/15349 (afr: add replication events) posted (#1) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/15349 (afr: add replication events) posted (#2) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/15349 (afr: add replication events) posted (#3) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/15349 (afr: add replication events) posted (#4) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/15349 (afr: add replication events) posted (#5) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/15349 (afr: add replication events) posted (#6) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/15349 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 86e312d872a957afff1e508f13f62c4102dba22d Author: Ravishankar N <ravishankar> Date: Thu Sep 1 13:01:22 2016 +0530 afr: add replication events Added the following events for the eventing framework: "EVENT_AFR_QUORUM_MET", --> Sent when quorum is met. "EVENT_AFR_QUORUM_FAIL" -->Sent when quorum is lost. "EVENT_AFR_SUBVOL_UP" -->Sent when afr witnesses the first up subvolume. "EVENT_AFR_SUBVOLS_DOWN"-->Sent when all children of an afr subvol are down. "EVENT_AFR_SPLIT_BRAIN" -->Sent when self-heal detects split-brain in heal path (not read/write path). Change-Id: I937c61ca1ce78b5922ade73c7bfa3051df59c513 BUG: 1371485 Signed-off-by: Ravishankar N <ravishankar> Reviewed-on: http://review.gluster.org/15349 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Pranith Kumar Karampuri <pkarampu> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org>
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.10.0, please open a new bug report. glusterfs-3.10.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/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/