[Bugs] [Bug 1276060] dist-geo-rep: geo-rep status shows Active/Passive even when all the gsync processes in a node are killed

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1276060



--- Comment #5 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12448 committed in release-3.7 by Vijay
Bellur (vbellur at redhat.com) 
------
commit e3b48d847492b831487a8539e3e726706959ac2f
Author: Saravanakumar Arumugam <sarumuga at redhat.com>
Date:   Mon Aug 10 18:42:05 2015 +0530

    geo-rep: Update geo-rep status, if monitor process is killed

    Problem:
    When the monitor process itself is getting killed, geo-rep session
    still shows as active.

    Status command will just pick up the content from the status file
    to show the output. Monitor process is the one which updates the Status
file.

    When the monitor process itself gets killed, there is no way to update
    the status file. So, geo-rep session status command ends up showing
    last updated Status present in the status file.

    Solution:
    While getting the status output, check whether monitor process is running.
    If it is NOT running, update the status as STOPPED.

    Change-Id: I86a7ac1746dd8f27eef93658e992ef16f6068d9d
    BUG: 1276060
    Signed-off-by: Saravanakumar Arumugam <sarumuga at redhat.com>
    Reviewed-on: http://review.gluster.org/11873
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Milind Changire <mchangir at redhat.com>
    Reviewed-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy at redhat.com>
    (cherry picked from commit 4d4c7d5dc54850dcf916083b2b1398d9bfe2bfe6)
    Reviewed-on: http://review.gluster.org/12448
    Reviewed-by: Aravinda VK <avishwan at redhat.com>
    Reviewed-by: Vijay Bellur <vbellur at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.