[Gluster-users] ec2 peers
greno at verizon.net
Wed Jan 19 17:27:57 UTC 2011
Ok, so I attached elastic ips and then probed the secondary server from
the primary using the external dns name. And the probe succeeds and I
see the external DNS name along with a UUID. However, on the secondary
server if I query peer status it is now showing the Internal IP of the
primary server. So where did that peer entry come from? I did not
probe from the secondary? Can I safely detach this IP and then probe
from the secondary to the primary based on external DNS name? Or is
this IP entry going to continue to happen automatically?
On 01/19/2011 12:09 PM, Gerry Reno wrote:
> That's exactly what I was thinking as well. Unless glusterfs has some
> magic discovery mechanism based on UUID's.
> And I believe that within the EC2 network even external EC2 DNS names
> get resolved to the internal IP so no add'l network charges should be
> On 01/19/2011 11:52 AM, Rafiq Maniar wrote:
>> For "reboots", instances keep the same internal and external IP.
>> If you stop and start them, they get a new IP.
>> What I did to get around this problem was I used ElasticIPs for the 2
>> servers, to ensure they always had the same DNS address. I then use
>> the full
>> external DNS name when setting up Gluster.
>> On Wed, Jan 19, 2011 at 4:45 PM, Gerry Reno <greno at verizon.net
>> <mailto:greno at verizon.net>> wrote:
>> I have glusterfs running on ec2.
>> I am able to successfully probe for the peer, but considering this
>> is on
>> ec2 and the internal IP could possibly change later on if say the AMI
>> got hung and had to be restarted then how does glusterfs react in that
>> situation? Can it still find the peers?
>> Gluster-users mailing list
>> Gluster-users at gluster.org <mailto:Gluster-users at gluster.org>
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users