<div dir="ltr"><div style="font-family:arial,sans-serif;font-size:13px">Hi All,</div><div style="font-family:arial,sans-serif;font-size:13px">I'm currently setting up a distributed volume over 3 peers (each peer is a compute server with multiple Ethernet ports). </div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">I would like to connect each peer to all other peers with a direct connection, so that traffic between peers does not affect external network traffic (e.g. accessing the volume via other clients).</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">I currently have each direct connection on its own subnet. And the /etc/hosts file on each peer configured accordingly. However when I add the 3rd peer using "gluster peer probe server3", the hostname displayed using "gluster peer status" on server2 shows the wrong IP address for server1 (as it is based on the IP address of the interface connecting server 1 and 3.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">To correct this, is it safe to manually edit the hostname in the /var/lib/glusterd/peers/UUID file? </div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">The other solution would be to have a separate switch/network for internal traffic. However I figure a direct connection between each peer will be faster. <br>
</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Thanks in advance!</div><div style="font-family:arial,sans-serif;font-size:13px">Dave</div>
<div><br></div>
</div>