[Bugs] [Bug 1238661] When bind-insecure is enabled, bricks may not be able to bind to port assigned by Glusterd

bugzilla at redhat.com bugzilla at redhat.com
Mon Jul 27 04:31:44 UTC 2015


--- Comment #5 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11512 committed in master by Raghavendra G
(rgowdapp at redhat.com) 
commit 9442e7bf80f5c2189140918bb5588868204521ed
Author: Prasanna Kumar Kalever <prasanna.kalever at redhat.com>
Date:   Wed Jun 24 12:21:02 2015 +0530

    rpc: fix binding brick issue while bind-insecure is enabled


    When bind-insecure is turned on (which is the default now), it may happen
    that brick is not able to bind to port assigned by Glusterd for example

    It seems to occur because the rpc_clnt connections are binding to ports in
    the same range. so brick fails to bind to a port which is already used by
    someone else


    fix for now is to  make rpc_clnt to get port numbers from 65535 in a
    order, as a result port clash is minimized

    other fixes:

    previously rdma binds to port >= 1024 if it cannot find a free port < 1024,
    even when bind insecure was turned off(ref to commit '0e3fd04e'), this
    add's a check for bind-insecure in gf_rdma_client_bind function

    This patch also re-enable bind-insecure and allow insecure by default which
    reverted (ref: commit cef1720) previously

    Change-Id: Ia1cfa93c5454e2ae0ff57813689b75de282ebd07
    BUG: 1238661
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever at redhat.com>
    Reviewed-on: http://review.gluster.org/11512
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp 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=pEK6PH2WKH&a=cc_unsubscribe

More information about the Bugs mailing list