<div><div dir="auto">If the gluster nodes are peer probed through FQDNs then you’re good. If they’re done through IPs then for every node you’d need to replace the old IP with new IP for all the files in /var/lib/glusterd along with renaming the filenames with have the associated old IP and restart all gluster services. I used to have a script for this which I shared earlier in users ML, need to dig through my mailbox and find it. </div><br><div class="gmail_quote"><div>On Sun, 29 Oct 2017 at 18:45, Hemant Mamtora <<a href="mailto:hemantrm@hotmail.com">hemantrm@hotmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks,<br>
<br>
We have a 12 node replicated gluster with 2 X 6.<br>
<br>
I need to change IP address in 6 nodes out of the 12 nodes, keeping the<br>
host name same. The 6 nodes that I plan to change IP are part of the 3<br>
sub-volumes.<br>
<br>
Is this possible and if so is there any formal process to tell that<br>
there is a change in IP address.<br>
<br>
My requirement is to keep the volume up and not bring it down. I can<br>
change IP address for the nodes one at a time. When a IP change is done<br>
that node will be rebooted as well.<br>
<br>
Many thanks in advance.<br>
<br>
--<br>
- Hemant Mamtora<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div></div><div dir="ltr">-- <br></div><div class="gmail_signature" data-smartmail="gmail_signature">- Atin (atinm)</div>