<div dir="ltr"><div><div><div><div><div>Hi,<br><br></div>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"<br></div><br></div>This is what I expected :<br><br></div>server0 : glusterd 24007 + glusterfsd 49152<br>server1 : glusterd 24007 + glusterfsd 49152<br></div><div>server2 : glusterd 24007 + glusterfsd 49152<br></div><div><div><div><div><div><div><div><br></div><div>and this is what I really get :<br><br>server0 : glusterd 24007 + glusterfsd 49156<br>server1 : glusterd 24007 + glusterfsd 49152<br>server2 : glusterd 24007 + glusterfsd 49155<br><br></div><div>I launch all my commands (gluster volume start/stop/status/info) from server1.<br><br></div><div>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.<br><br></div><div>server0 :<br> server0/listen-port=49156<br> server1/listen-port=0<br></div><div> server2/listen-port=0<br><br></div><div>server1 :<br></div><div> server0/listen-port=0<br> server1/listen-port=49155<br> server2/listen-port=0<br><br>server2 :<br> server0/listen-port=0<br> server1/listen-port=0<br> server2/listen-port=49152<br><br></div><div>What's the cause of this?<br><br></div><div>The "brick" logs on all servers say something specific :<br><br>On "server0" :<br>I [graph.c:269:gf_add_cmdline_options] 0-TEST-server: adding option 'listen-port' for<br>volume 'TEST-server' with value '49156'<br><br></div><div>On "server1" :<br>I [graph.c:269:gf_add_cmdline_options] 0-TEST-server: adding option 'listen-port' for<br>volume 'TEST-server' with value '49155'<br></div><div><br></div><div>On "server2" :<br>I [graph.c:269:gf_add_cmdline_options] 0-TEST-server: adding option 'listen-port' for<br>volume 'TEST-server' with value '49152'<br></div><div><br></div><div>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.<br></div><div><br></div><div>Did I understand wrong about the port assignment or is there something off with my test setup?<br></div><div><br></div><div>BTW, they all complain about the same thing :<br><br>W [options.c:898:xl_opt_validate] 0-TEST-server: option 'listen-port' is deprecated, preferred is 'transport.socket.listen-port', continuing with correction<br></div><div><br>-- <br><div class="gmail_signature">Unix _IS_ user friendly, it's just selective about who its friends are.</div>
</div></div></div></div></div></div></div></div>