Not at all a problem. I am here to help Rarylson :)
-Atin
Sent from one plus one
On Jul 2, 2015 7:23 PM, "Rarylson Freitas" wrote:
> Hi Atin,
>
> You are right!!! I was using the version 3.5 in production. And when I've
> checked the Gluster source code, I checked the wrong commit (not the lates
Hi Atin,
You are right!!! I was using the version 3.5 in production. And when I've
checked the Gluster source code, I checked the wrong commit (not the latest
commit in the master branch).
Currently, you've already implemented my the proposed solution. It was done
at the function gd_peerinfo_find
Which gluster version are you using? Better peer identification feature
(available 3.6 onwards) should tackle this problem IMO.
~Atin
On 07/02/2015 10:05 AM, Rarylson Freitas wrote:
> Hi,
>
> Recently, my company needed to change our hostnames used in the Gluster
> Pool.
>
> In a first moment,
Hi,
Recently, my company needed to change our hostnames used in the Gluster
Pool.
In a first moment, we have two Gluster Nodes called storage1 and storage2.
Our volumes used two bricks: storage1:/MYVOLYME and storage2:/MYVOLUME. We
put the storage1 and storage2 IPs in the /etc/hosts file of our n
