Thanks Atin. Peer probes were done using FQDN and I was able to make these changes.
The only thing I had to do on rest of the nodes was to flush nscd; after that everything was good and I did not have to restart gluster services on these rest of the nodes. - Hemant On 10/30/17 11:46 AM, Atin Mukherjee wrote: 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. On Sun, 29 Oct 2017 at 18:45, Hemant Mamtora <heman...@hotmail.com<mailto:heman...@hotmail.com>> wrote: Folks, We have a 12 node replicated gluster with 2 X 6. I need to change IP address in 6 nodes out of the 12 nodes, keeping the host name same. The 6 nodes that I plan to change IP are part of the 3 sub-volumes. Is this possible and if so is there any formal process to tell that there is a change in IP address. My requirement is to keep the volume up and not bring it down. I can change IP address for the nodes one at a time. When a IP change is done that node will be rebooted as well. Many thanks in advance. -- - Hemant Mamtora _______________________________________________ Gluster-users mailing list Gluster-users@gluster.org<mailto:Gluster-users@gluster.org> http://lists.gluster.org/mailman/listinfo/gluster-users -- - Atin (atinm) -- - Hemant Mamtora
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
