[Bugs] [Bug 1341068] [geo-rep]: Monitor crashed with [Errno 3] No such process

[bugzilla at redhat.com]

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



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14562 committed in release-3.7 by Aravinda VK
(avishwan at redhat.com) 
------
commit 0e3b6f39924d8d1ef3b5fa57b5d38886b5d3626e
Author: Aravinda VK <avishwan at redhat.com>
Date:   Tue May 24 14:13:29 2016 +0530

    geo-rep: Handle Worker kill gracefully if worker already died

    If Agent dies for any reason, monitor tries to kill Worker also. But
    if worker is also died then kill command raises error ESRCH: No such
    process.

    [2016-05-23 16:49:33.903965] I [monitor(monitor):326:monitor] Monitor:
        Changelog Agent died, Aborting Worker(/bricks/brick0/master_brick0)
    [2016-05-23 16:49:33.904535] E
[syncdutils(monitor):276:log_raise_exception]
        <top>: FAIL:
    Traceback (most recent call last):
      File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 306
in
      twrap
        tf(*aa)
      File "/usr/libexec/glusterfs/python/syncdaemon/monitor.py", line 393, in
      wmon
         slave_host, master)
      File "/usr/libexec/glusterfs/python/syncdaemon/monitor.py", line 327, in
      monitor
         os.kill(cpid, signal.SIGKILL)
         OSError: [Errno 3] No such process

    With this patch, monitor will gracefully handle if worker is already died.

    Change-Id: I3ae5f816a3a197343b64540cf46f5453167fb660
    Signed-off-by: Aravinda VK <avishwan at redhat.com>
    BUG: 1341068
    Reviewed-on: http://review.gluster.org/14512
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    (cherry picked from commit 4f4a94a35a24d781f3f0e584a8cb59c019e50d6f)
    Reviewed-on: http://review.gluster.org/14562
    Reviewed-by: Saravanakumar Arumugam <sarumuga at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=A9BL9D8Dj5&a=cc_unsubscribe