[Gluster-users] GlusterFS Mounts at startup consuming needed local ports for host services

[Ryan.J.Wyler at wellsfargo.com]

Is there any way to configure glusterfs to avoid using specific local ports when mounting filesystems?

Ryan Wyler

From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Ryan.J.Wyler at wellsfargo.com
Sent: Friday, April 08, 2016 9:31 AM
To: gluster-users at gluster.org
Subject: [Gluster-users] GlusterFS Mounts at startup consuming needed local ports for host services

Glusterfs mounts are squashing ports I need available for services, specifically on port 1002.

How can I configure glusterfs mount points to avoid specific local ports for the connections?

A potential workaround I thought of is removing the mounts from starting automatically at startup and create an rc.d startup script to mount the glusterfs filesystems after all the host services have started to avoid those ports.

Is there a different option?

The local port range is using 1000-1023 as seen in the information below for client.domain.com.

# lsof | grep glusterfs | grep IPv4
glusterfs  2893    root    9u     IPv4              15373       0t0                  TCP client.domain.com:1023->server1.domain.com:24007 (ESTABLISHED)
glusterfs  2893    root   10u     IPv4              15447       0t0                  TCP client.domain.com:1015->server2.domain.com:49171 (ESTABLISHED)
glusterfs  2893    root   11u     IPv4              15446       0t0                  TCP client.domain.com:1016->server3.domain.com:49171 (ESTABLISHED)
glusterfs  2893    root   13u     IPv4              15422       0t0                  TCP client.domain.com:1020->server1.domain.com:49171 (ESTABLISHED)
glusterfs  2893    root   15u     IPv4              15439       0t0                  TCP client.domain.com:1018->server4.domain.com:49171 (ESTABLISHED)
glusterfs  2998    root    9u     IPv4              15523       0t0                  TCP client.domain.com:1014->server1.domain.com:24007 (ESTABLISHED)
glusterfs  2998    root   10u     IPv4              15588       0t0                  TCP client.domain.com:1006->server2.domain.com:49157 (ESTABLISHED)
glusterfs  2998    root   11u     IPv4              15576       0t0                  TCP client.domain.com:1007->server3.domain.com:49157 (ESTABLISHED)
glusterfs  2998    root   14u     IPv4              15549       0t0                  TCP client.domain.com:1012->server1.domain.com:49157 (ESTABLISHED)
glusterfs  2998    root   16u     IPv4              15569       0t0                  TCP client.domain.com:1009->server4.domain.com:49157 (ESTABLISHED)
glusterfs 46813    root   10u     IPv4             342418       0t0                  TCP client.domain.com:1019->server1.domain.com:24007 (ESTABLISHED)
glusterfs 46813    root   11u     IPv4             342445       0t0                  TCP client.domain.com:busboy->server2.domain.com:49152 (ESTABLISHED)
glusterfs 46813    root   15u     IPv4             342428       0t0                  TCP client.domain.com:surf->server1.domain.com:49152 (ESTABLISHED)
glusterfs 46813    root   16u     IPv4             342434       0t0                  TCP client.domain.com:1002->server4.domain.com:49152 (ESTABLISHED)
glusterfs 46813    root   17u     IPv4             342440       0t0                  TCP client.domain.com:cadlock2->server3.domain.com:49152 (ESTABLISHED)


Glusterfs RPMs installed:

glusterfs-libs-3.6.0.54-1
glusterfs-api-3.6.0.54-1
glusterfs-fuse-3.6.0.54-1
glusterfs-3.6.0.54-1



Ryan Wyler
Ryan.j.wyler at wellsfargo.com<mailto:Ryan.j.wyler at wellsfargo.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160409/6da4c226/attachment.html>