There is a small note in the documentation that tells you it is easier to use hostnames when adding peers. If you don't have a DNS that can be easily achieved with the hosts-file. For now you could try to add the new IP as peer and then (I'm not 100% sure with this) if it doesn't integrate the brick, use the replace-brick command. -----Original Mail----- From: Pradeep Shettar [pradeep.shettar25 at gmail.com] Sent: 29.07.13 - 14:09:58 To: gluster-users at gluster.org Subject: Brick offline due to change of node's ip > Hi all, > ???????? I have a setup of glusterfs with one client and two nodes. > Everything was running smooth until after some days one of the node's ip > changed. > From node 1: > [root at unused brick1]# gluster volume status gv1 > Status of volume: gv1 > Gluster process??? ??? ??? ??? ??? ?? ? ? ? ? ?? Port??? Online??? Pid > ------------------------------------------------------------------------------ > Brick 10.70.1.105:/export/brick1??? ???? 24010??? Y??? 1229 > NFS Server on localhost??? ??? ??? ??? ??? 38467???? Y??? 1228 > Self-heal Daemon on localhost??? ??? ??? ? N/A?? ? Y??? 1235 > NFS Server on 10.70.1.105??? ??? ??? ??? 38467??? Y??? 1236 > Self-heal Daemon on 10.70.1.105??? ??? ?? N/A??? Y??? 1242 > > from node 2: > [root at unused brick1]# gluster volume status gv1 > Status of volume: gv1 > Gluster process??? ??? ??? ??? ??? ?? ? ? ? ? ? ? Port??? Online??? Pid > ------------------------------------------------------------------------------ > Brick 10.70.1.105:/export/brick1??? ??? ?? 24010?? ? Y?? ?? 1229 > NFS Server on localhost??? ??? ??? ??? ?? ? ? 38467??? Y?????? 1236 > Self-heal Daemon on localhost??? ??? ??? ??? N/A?? ?? Y?? ? ? 1242 > > help appreciated > > with regards > Pradeep Shettar
