TCP port usage

[Melkor Lord <melkor.lord@xxxxxxxxx>]

Hi,

To my understanding, Gluster starts volumes TCP services at port 49152 and then increases the port number with every new volume right? I have a 3 replica test environment with only one volume "TEST"

This is what I expected :

server0 : glusterd 24007 + glusterfsd 49152
server1 : glusterd 24007 + glusterfsd 49152

server2 : glusterd 24007 + glusterfsd 49152

and this is what I really get :

server0 : glusterd 24007 + glusterfsd 49156
server1 : glusterd 24007 + glusterfsd 49152
server2 : glusterd 24007 + glusterfsd 49155

I launch all my commands (gluster volume start/stop/status/info) from server1.

I checked the configuration files under /var/lib/gluster/glusterd/vols/TEST/bricks and the TCP is "hardcoded" for some servers but not for others.

server0 :
  server0/listen-port=49156
  server1/listen-port=0

  server2/listen-port=0

server1 :

  server0/listen-port=0
  server1/listen-port=49155
  server2/listen-port=0

server2 :
  server0/listen-port=0
  server1/listen-port=0
  server2/listen-port=49152

What's the cause of this?

The "brick" logs on all servers say something specific :

On "server0" :
I [graph.c:269:gf_add_cmdline_options] 0-TEST-server: adding option 'listen-port' for
volume 'TEST-server' with value '49156'

On "server1" :
I [graph.c:269:gf_add_cmdline_options] 0-TEST-server: adding option 'listen-port' for
volume 'TEST-server' with value '49155'

On "server2" :
I [graph.c:269:gf_add_cmdline_options] 0-TEST-server: adding option 'listen-port' for
volume 'TEST-server' with value '49152'

I stopped the volume, I edited each brick config file on each server to set the port to "0" and even changed "listen-port" to "transport.socket.listen-port" (see below). Starting the volume again did reset everything the way it was before my changes, even "listen-port", so I guess that these "brick" files are dynamically created upon volume start.

Did I understand wrong about the port assignment or is there something off with my test setup?

BTW, they all complain about the same thing :

W [options.c:898:xl_opt_validate] 0-TEST-server: option 'listen-port' is deprecated, preferred is 'transport.socket.listen-port', continuing with correction

--

Unix _IS_ user friendly, it's just selective about who its friends are.

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users