[Bugs] [Bug 1453086] Brick Multiplexing: On reboot of a node Brick multiplexing feature lost on that node as multiple brick processes get spawned

[bugzilla at redhat.com]

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



--- Comment #4 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17383 committed in release-3.11 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit 71752f1bde9e8ad7a71670c885279f91ff951a1b
Author: Samikshan Bairagya <samikshan at gmail.com>
Date:   Tue May 23 19:32:24 2017 +0530

    glusterd: Eliminate race in brick compatibility checking stage

    In https://review.gluster.org/17307/, while looking for compatible
    bricks for multiplexing, it is checked if the brick pidfile exists
    before checking if the corresponding brick process is running.

    However checking if the brick process is running just after
    checking if the pidfile exists isn't enough since there might be
    race conditions where the pidfile has been created but hasn't
    been updated with a pid value yet. This commit solves that by
    making sure that we wait iteratively till the pid value is updated
    as well.

    > Reviewed-on: https://review.gluster.org/17375
    > Smoke: Gluster Build System <jenkins at build.gluster.org>
    > Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    > NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

    (cherry picked from commit a8624b8b13a1f4222e4d3e33fa5836d7b45369bc)

    Change-Id: Ib7a158f95566486f7c1f84b6357c9b89e4c797ae
    BUG: 1453086
    Signed-off-by: Samikshan Bairagya <samikshan at gmail.com>
    Reviewed-on: https://review.gluster.org/17383
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

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