I always thought it retried for another IP after a timeout, though I haven't test it. -Tony --------------------------- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abiacco at formatdynamics.com http://www.formatdynamics.com <http://www.formatdynamics.com/> From: Jos? Celano [mailto:jcelano at iqingenieros.com] Sent: Monday, May 23, 2011 11:40 AM To: Anthony J. Biacco Cc: Joshua Baker-LePain; gluster-users at gluster.org Subject: Re: Scaling Gluster I have though about this, It is the solution scalr offers, but the problem remains the same. What happen if the host which the dns mapped to is down? This solution solves load balancing but no high availability. On Mon, May 23, 2011 at 6:29 PM, Anthony J. Biacco <abiacco at formatdynamics.com> wrote: Make a DNS round-robin host entry that points to both IP addresses, then use that hostname in the mount command -Tony --------------------------- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abiacco at formatdynamics.com http://www.formatdynamics.com <http://www.formatdynamics.com/> From: Jos? Celano [mailto:jcelano at iqingenieros.com] Sent: Monday, May 23, 2011 11:06 AM To: Anthony J. Biacco Cc: Joshua Baker-LePain; gluster-users at gluster.org Subject: Re: Scaling Gluster Hi Tony: On Mon, May 23, 2011 at 4:55 PM, Anthony J. Biacco <abiacco at formatdynamics.com> wrote: I think i read somewhere the server in the mount string is only used to retrieve the cluster config. So as long as that server is up at time of mount, you're fine. Yes, It is in the offcial documentation. I am trying to avoid that. My final objetive is high availability. If the server goes down after mount, it doesnt matter as the cluster config on the mounting servers knows about all gluster servers. Yes, there is no problem after mounting becasuse I use replication. The problem is in new mountig processes after the seleted "master gluster server" crashes. Somebody correct me if i'm wrong. Personally, i copy the cluster config to all my mounting servers and use that file in the mount command instead of a gluster server hostname. Yes. That is ok, but I am finding an automatic way in case I make an auto-scalable Gluster deployment. If something change in Gluster like the number of servers (I could add more servers later) then I would have to copy the new volumen info to my Apache Rol Amazon Image, and this can not be done automatically. Other way could be doing a script to load that file from S3 but I would have to copy the new volume info file to S3 every time It changes, and I don?t know how this can be done because I don?t know how monitoring and catch Gluster volumes changes. -Tony -----Original Message----- From: Joshua Baker-LePain <jlb17 at duke.edu> Sent: May 23, 2011 9:16 AM To: Jos? Celano <jcelano at iqingenieros.com> Cc: gluster-users at gluster.org <gluster-users at gluster.org> Subject: Re: Scaling Gluster On Thu, 19 May 2011 at 12:40am, Jos? Celano wrote > I have 2 replicated servers and several Apache servers that mount the same > volume. > When I mount a Gluster Volumen from one of the Apache servers > > mount.glusterfs > ip-XX-XXX-XXX-XXX.eu-west-1.compute.internal:/dab578f4-06fa-4584-ac1d-c6ef14e6d0cf > /mnt/glusterfs > how could I obtain high availability if that server die? Use ucarp to share a virtual IP address between the Gluster servers, and mount using that IP address. -- Joshua Baker-LePain QB3 Shared Cluster Sysadmin UCSF -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20110523/55406762/attachment.htm>
