[Gluster-users] changes to client port range in release 3.1.3

Vijay Bellur vbellur at redhat.com
Wed May 4 02:09:58 UTC 2016

On Tue, May 3, 2016 at 5:28 AM, Prasanna Kalever <pkalever at redhat.com> wrote:

> If we see the ephemeral port standards
> 1.  The Internet Assigned Numbers Authority (IANA) suggests the range
> 49152 to 65535
> 2.  Many Linux kernels use the port range 32768 to 61000
> more at [2]
> Some of our thoughts include split the current brick port range ( ~16K
> ) into two (may be ~8K each or some other ratio) and use them for
> client and bricks, which could solve the problem but also  introduce a
>  limitation for scalability.

I would recommend providing the administrator an ability to override
any logic that we use to implement this behavior.

> The patch [1] goes in 3.1.3, we wanted know if there are any impacts
> caused with these changes.
> [1] http://review.gluster.org/#/c/13998/

I would have ideally liked the patch to have spent some time in the
review queue after this email was sent. It does look like the patch
got merged within 2 hours after the email was sent. This interval is
grossly inadequate if you are looking to obtain any feedback that can
add value. Nevertheless I have provided my comments on the patchset.
Please incorporate them in a subsequent commit.


More information about the Gluster-users mailing list