[Gluster-users] Proper procedure for changing the IP address of a glustefs server

[Mark Morlino]

Thank you for the replies Joe and Carlos.

Joe, I have tried probing from another peer several times, although perhaps
not in the correct sequence?
The bricks are setup using hostnames, however when I mount a volume with a
brick on the changed server I never see network connections to the new IP
address from the client.

It looks like this (that is the old IP address):

*[root at gluster2 ~]# gluster peer status*

*Number of Peers: 3*

 *Hostname: 10.10.113.99*

*Uuid: 9b5b5408-36f7-4090-b308-2a5b37dbe109*

*State: Peer in Cluster (Connected)*


*Hostname: gluster4*

*Uuid: ee9c307e-af6e-48c5-ae88-e6ed3bb35e5e*

*State: Peer in Cluster (Connected)*


*Hostname: gluster6*

*Uuid: 5904643e-d9a0-41e4-8672-dcef488d2e1b*

*State: Peer in Cluster (Connected)*

There is no network traffic to/from 10.10.113.99:

*[root at gluster2 ~]# ss -n | grep 10.10.113.99*

The new IP is 10.10.19.120 and there are many connections to it:

*[root at gluster2 ~]# host gluster3*

*gluster3 has address 10.10.19.120*

*[root at gluster2 ~]# ss -n | grep 10.10.19.120 | wc -l *

*94*

Probing by name does not seem to change anything:

*[root at gluster2 ~]# gluster peer probe gluster3*

*peer probe: success: host gluster3 port 24007 already in peer list*

*[root at gluster2 ~]# gluster peer status*

*Number of Peers: 3*


 *Hostname: 10.10.113.99*

*Uuid: 9b5b5408-36f7-4090-b308-2a5b37dbe109*

*State: Peer in Cluster (Connected)*


*Hostname: gluster4*

*Uuid: ee9c307e-af6e-48c5-ae88-e6ed3bb35e5e*

*State: Peer in Cluster (Connected)*


*Hostname: gluster6*

*Uuid: 5904643e-d9a0-41e4-8672-dcef488d2e1b*

*State: Peer in Cluster (Connected)*




On Sun, May 18, 2014 at 1:38 PM, Carlos Capriotti <
capriotti.carlos at gmail.com> wrote:

> Mark, hi.
>
> 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:
>
> 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.
>
> Final result: changing IPs caused all to go south, and I had to start from
> scratch.
>
> 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.
>
> 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.
>
> Probably a good feature request for 3.6.
>
> Cheers,
>
> Carlos
>
>
>
> On Sat, May 17, 2014 at 1:33 AM, Mark Morlino <mark at gina.alaska.edu>wrote:
>
>> Perhaps someone here can help me.
>>
>> I have had to change the IP address of one of my GlusterFS servers. They
>> are all 3.4.0.
>>
>> 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.
>>
>> On the server with the new IP, gluster peer status shows the other peers
>> correctly with their hostnames and as being connected.
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> Thanks,
>> -Mark
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140519/d6783ba6/attachment.html>