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 incurred. Regards, Gerry On 01/19/2011 11:52 AM, Rafiq Maniar wrote: > Hi, > > 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 > GlusterFS > servers, to ensure they always had the same DNS address. I then use > the full > external DNS name when setting up Gluster. > > Rafiq > > 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? > > > Regards, > Gerry > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org <mailto:Gluster-users at gluster.org> > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > >
