Bug 1279362

Summary: Monitor should restart the worker process when Changelog agent dies
Product: [Community] GlusterFS Reporter: Aravinda VK <avishwan>
Component: geo-replicationAssignee: Aravinda VK <avishwan>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.5CC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1277076 Environment:
Last Closed: 2016-02-15 06:26:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1277076    
Bug Blocks:    

Description Aravinda VK 2015-11-09 09:53:33 UTC
+++ This bug was initially created as a clone of Bug #1277076 +++

Description of problem:

Geo-replication will not detect if Changelog agent dies. Status shows all good but without any progress since Changelog Agent is not available.


Version-Release number of selected component (if applicable):
Mainline and 3.7.x

How reproducible:
Always


Steps to Reproduce:
1. Start Geo-replication and Wait till Status becomes "Active"
2. Kill Agent process and check the Geo-replication status(ps aux | grep gsyncd | grep agent)


Actual results:
Status shows "Active" even though status is "Faulty"

Expected results:
Status should show "Faulty" and Monitor should respawn the worker

--- Additional comment from Vijay Bellur on 2015-11-02 04:34:34 EST ---

REVIEW: http://review.gluster.org/12485 (geo-rep: Kill Geo-rep Worker when Agent process dies) posted (#1) for review on master by Aravinda VK (avishwan)

--- Additional comment from Vijay Bellur on 2015-11-02 06:49:57 EST ---

REVIEW: http://review.gluster.org/12485 (geo-rep: Kill Geo-rep Worker when Agent process dies) posted (#2) for review on master by Aravinda VK (avishwan)

Comment 1 Aravinda VK 2015-11-09 09:55:16 UTC
Patch sent Upstream for review
http://review.gluster.org/#/c/12550/

Comment 2 Vijay Bellur 2015-11-25 07:17:08 UTC
COMMIT: http://review.gluster.org/12550 committed in release-3.7 by Venky Shankar (vshankar) 
------
commit a694e86cd5340fff1143e2ac55ec908d3ef890b3
Author: Aravinda VK <avishwan>
Date:   Fri Oct 30 17:06:58 2015 +0530

    geo-rep: Kill Geo-rep Worker when Agent process dies
    
    When Changelog agent process dies, Geo-replication fails to detect
    and worker will run without respective Changelog agent. Status shows
    Active/Passive without any progress.
    
    With this patch, Worker process gets killed whenever Changelog
    agent dies.
    
    Change-Id: I30b4cc77f924f7e8174b8bfe415ac17f0b3851b4
    Signed-off-by: Aravinda VK <avishwan>
    BUG: 1279362
    Reviewed-on: http://review.gluster.org/12485
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Venky Shankar <vshankar>
    Reviewed-by: Kotresh HR <khiremat>
    (cherry picked from commit 5d1ff7efd6ab3bd29a29922a9ea1e1aaf02544ad)
    Reviewed-on: http://review.gluster.org/12550

Comment 3 Kaushal 2016-04-19 07:47:50 UTC
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.7, please open a new bug report.

glusterfs-3.7.7 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-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user