[Bugs] [Bug 1437494] Brick Multiplexing: Volume status still shows the PID even after killing the process

[bugzilla at redhat.com]

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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16971 committed in master by Jeff Darcy
(jeff at pl.atyp.us) 
------
commit e325479cf222d2f25dbc0a4c6b80bfe5a7f09f43
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Thu Mar 30 14:47:45 2017 +0530

    glusterd: reset pid to -1 if brick is not online

    While populating brick details in gluster volume status response payload
    if a brick is not online then pid should be reset back to -1 so that
    volume status output doesn't show up the pid which was not cleaned up
    especially with brick multiplexing where multiple bricks belong to same
    process.

    Change-Id: Iba346da9a8cb5b5f5dd38031d4c5ef2097808387
    BUG: 1437494
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: https://review.gluster.org/16971
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Gaurav Yadav <gyadav at redhat.com>
    Reviewed-by: Prashanth Pai <ppai at redhat.com>
    Reviewed-by: Jeff Darcy <jeff at pl.atyp.us>

-- 
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=OPRfpeAYS9&a=cc_unsubscribe