<div dir="ltr">Mark, hi.<div><br></div><div>Short answer to you, not because it does not deserve a long, detailed answer, but just because my experience won't add much to your own:</div><div><br></div><div>You did great by editing all files and having you cluster working again. I was not that lucky, and it was a good thing it was simply a test system; I configured my cluster using the IPs on all peers, because I had multihomed servers and wanted to use a given NIC/net for gluster back end.</div>
<div><br></div><div>Final result: changing IPs caused all to go south, and I had to start from scratch. </div><div><br></div><div>I posted the same question you did, with no answer at all, so, it leads me to believe this part of gluster is one of those black holes that need much improvement.</div>
<div><br></div><div>IMO, you need some sort of "bind to" capability here, but it is not that simple, after all, like in my case, I wanted back end traffic on one NIC, and client traffic on another.</div><div><br>
</div><div>Probably a good feature request for 3.6.</div><div><br></div><div>Cheers, </div><div><br></div><div>Carlos</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, May 17, 2014 at 1:33 AM, Mark Morlino <span dir="ltr"><<a href="mailto:mark@gina.alaska.edu" target="_blank">mark@gina.alaska.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Perhaps someone here can help me. </div><div><br></div>I have had to change the IP address of one of my GlusterFS servers. They are all 3.4.0.<div>
<br><div>It had been originally probed by hostname and "gluster peer status" on the other peers showed it's name. So, I shut it down, changed it's IP and booted it back up.</div>
<div><br></div><div>On the server with the new IP, gluster peer status shows the other peers correctly with their hostnames and as being connected.</div><div><br></div><div>On the other peers, the server with the changed IP showed up as it's old IP address (not the name) and as being disconnected. Peer probing the changed server by name from the other peers did not change anything.</div>
<div><br></div><div>One by one I stopped the glusterd service on the peers, and edited /var/lib/glusterd/peers/UUID for the changed server by replacing the old IP address with the hostname and then started the glusterd service.</div>
<div><br></div><div>Now the other peers display the changed server as being connected but using the old IP address as the hostname. Running ss shows that all of the peers are actually connected to the new IP address of the changed server. </div>
<div><br></div><div>Everything seems to be working but I have some reservations about leaving it like this and would be interested in any advice as to how it might be corrected.</div><div><br></div><div>Thanks,</div><div>
-Mark </div></div></div>
<br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>