[Bugs] [Bug 1246481] rpc: fix binding brick issue while bind-insecure is enabled

[bugzilla at redhat.com]

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



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11758 committed in release-3.7 by Raghavendra
G (rgowdapp at redhat.com) 
------
commit 5ebf298ec03bc929a4142e70ed105130cf9c58df
Author: Prasanna Kumar Kalever <prasanna.kalever at redhat.com>
Date:   Fri Jul 24 17:35:16 2015 +0530

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

    This patch is backport of http://review.gluster.org/#/c/11512/

    > problem:

    > 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
    > 49192-49195...
    >
    > 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
    >
    > solution:
    >
    > fix for now is to  make rpc_clnt to get port numbers from 65535 in a
    > descending
    > 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
patch
    > 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 was reverted (ref: commit cef1720) previously

    > Change-Id: Ia1cfa93c5454e2ae0ff57813689b75de282ebd07
    > BUG: 1238661
    > Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever at redhat.com>

    Change-Id: Iea55f9b2a57b5e24d3df2c5fafae12fe99e9dee0
    BUG: 1246481
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever at redhat.com>
    Reviewed-on: http://review.gluster.org/11758
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    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.
You are the assignee for the bug.