[Bugs] [Bug 1322805] [scale] Brick process does not start after node reboot

[bugzilla at redhat.com]

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



--- Comment #6 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13865 committed in master by Jeff Darcy
(jdarcy at redhat.com) 
------
commit 34899d71f21fd2b4c523b68ffb2d7c655c776641
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Thu Mar 31 11:01:53 2016 +0530

    glusterd: Allocate fresh port on brick (re)start

    There is no point of using the same port through the entire volume life
cycle
    for a particular bricks process since there is no guarantee that the same
port
    would be free and no other application wouldn't consume it in between the
    glusterd/volume restart.

    We hit a race where on glusterd restart the daemon services start followed
by
    brick processes and the time brick process tries to bind with the port
which was
    allocated by glusterd before a restart is been already consumed by some
other
    client like NFS/SHD/...

    Note : This is a short term solution as here we reduce the race window but
don't
    eliminate it completely. As a long term solution the port allocation has to
be
    done by glusterfsd and the same should be communicated back to glusterd for
book
    keeping

    Change-Id: Ibbd1e7ca87e51a7cd9cf216b1fe58ef7783aef24
    BUG: 1322805
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/13865
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy 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=iucONCE6pN&a=cc_unsubscribe