[Bugs] [Bug 1221623] glusterd: add brick command should re-use the port for listening which is freed by remove-brick.

[bugzilla at redhat.com]

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



--- Comment #24 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14939 committed in master by Jeff Darcy
(jdarcy at redhat.com) 
------
commit 7abed939a7cc61880aed7547f12ace80e6128170
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Mon Jul 18 12:54:38 2016 +0530

    glusterd: search for free port from base_port

    When a volume is deleted, the freed up ports are never considered for
further
    allocation since pmap_registry_alloc () always starts scanning from
last_alloc.
    So in use cases where gluster volumes are frequently created and deleted
    managing ports become nightmare as for every new volume creation ports need
to
    be opened up by the admin based on the volume topology.

    Solution: Instead of scanning from last_alloc, pmap_registry_alloc ()
always
    starts from base_port now. What that means is glusterd will always try to
find
    out the ports which have been freed from earlier volumes and reallocate
them for
    the newer ones. There could be possibilities that when a volume is stopped
and
    started back their brick ports are changed which is completely acceptible
IMHO.

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