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

[bugzilla at redhat.com]

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

            Bug ID: 1238661
           Summary: When bind-insecure is enabled, bricks may not be able
                    to bind to port assigned by Glusterd
           Product: GlusterFS
           Version: mainline
         Component: transport
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: rtalur at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of 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 be because the rpc_clnt connections are binding to ports in the
same range. One small fix for now could be to make rpc_clnt to get port numbers
from 65535 in a descending order.

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