Hi Tony:<br><br><div class="gmail_quote">On Mon, May 23, 2011 at 4:55 PM, Anthony J. Biacco <span dir="ltr"><<a href="mailto:abiacco@formatdynamics.com">abiacco@formatdynamics.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
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.<br></blockquote><div><br>Yes, It is in the offcial documentation.<br>
I am trying to avoid that. My final objetive is high availability.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
If the server goes down after mount, it doesnt matter as the cluster config on the mounting servers knows about all gluster servers.<br></blockquote><div><br>Yes, there is no problem after mounting becasuse I use replication. The problem is in new mountig processes<br>
after the seleted "master gluster server" crashes.<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Somebody correct me if i'm wrong.<br>
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.<br></blockquote><div><br>Yes. That is ok, but I am finding an automatic way in case I make an auto-scalable Gluster deployment.<br>
If something change in Gluster like the number of servers (I could add more servers later) then I would have<br>to copy the new volumen info to my Apache Rol Amazon Image, and this can not be done automatically.<br>Other way could be doing a script to load that file from S3 but I would have to copy the new volume info file<br>
to S3 every time It changes, and I don´t know how this can be done because I don´t know how monitoring<br>and catch Gluster volumes changes.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
-Tony<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Joshua Baker-LePain <<a href="mailto:jlb17@duke.edu">jlb17@duke.edu</a>><br>
Sent: May 23, 2011 9:16 AM<br>
To: José Celano <<a href="mailto:jcelano@iqingenieros.com">jcelano@iqingenieros.com</a>><br>
Cc: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a> <<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>><br>
Subject: Re: [Gluster-users] Scaling Gluster<br>
<br>
On Thu, 19 May 2011 at 12:40am, José Celano wrote<br>
<br>
> I have 2 replicated servers and several Apache servers that mount the same<br>
> volume.<br>
> When I mount a Gluster Volumen from one of the Apache servers<br>
><br>
> mount.glusterfs<br>
> ip-XX-XXX-XXX-XXX.eu-west-1.compute.internal:/dab578f4-06fa-4584-ac1d-c6ef14e6d0cf<br>
> /mnt/glusterfs<br>
> how could I obtain high availability if that server die?<br>
<br>
Use ucarp to share a virtual IP address between the Gluster servers, and<br>
mount using that IP address.<br>
<br>
--<br>
Joshua Baker-LePain<br>
QB3 Shared Cluster Sysadmin<br>
UCSF<br>
<br>
</div></div></blockquote></div><br>