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

bugzilla at redhat.com bugzilla at redhat.com
Fri Jul 24 12:24:24 UTC 2015


            Bug ID: 1246481
           Summary: rpc: fix binding brick issue while bind-insecure is
           Product: GlusterFS
           Version: 3.7.3
         Component: core
          Assignee: bugs at gluster.org
          Reporter: prasanna.kalever at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com

Description of problem:

backporting http://review.gluster.org/#/c/11512/


    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

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list