Other solution I have been thinking in is making a script that before mounting the volume<br>in the client side makes a previous test (perhaps ping or even the same mount command)<br>and if this test fails It just tries it with the next Gluster server in the list. The problem here<br>
is to obtain the dynamic list of all gluster severs. I am using <a href="http://sclar.net">sclar.net</a> and they do that job for<br>me. There is a directory in every instance where they automatically put all active server IPs for every rol.<br>
<br>But I am finding a simpler solution because <span class="clickable"> <span class="qex">I thought it is strange that</span></span> Gluster don´t have<br>a way of doing this internally. Perhaps It could be done adding a gluster mount command with 2 o 3<br>
"master servers" location parameters and that it chooses internally the first is not down (like DNS).<br><br><br><div class="gmail_quote">On Mon, May 23, 2011 at 5:15 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 don't expect and haven't made many volume changes, so the maintenance involved transferring files every so often versus maintenance of another puzzle piece that can fail is a no brainer for me.<br>
But I'm sure many others have more complicated and ever changing setups than me.<br>
<br>
-Tony<br>
---------------------------<br>
Manager, IT Operations<br>
Format Dynamics, Inc.<br>
P: <a href="tel:303-228-7327" value="+13032287327">303-228-7327</a><br>
F: <a href="tel:303-228-7305" value="+13032287305">303-228-7305</a><br>
<a href="mailto:abiacco@formatdynamics.com">abiacco@formatdynamics.com</a><br>
<a href="http://www.formatdynamics.com" target="_blank">http://www.formatdynamics.com</a><br>
<div><div></div><div class="h5"><br>
<br>
> -----Original Message-----<br>
> From: Joshua Baker-LePain [mailto:<a href="mailto:jlb17@duke.edu">jlb17@duke.edu</a>]<br>
> Sent: Monday, May 23, 2011 10:02 AM<br>
> To: Anthony J. Biacco<br>
> Cc: José Celano; <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> Subject: RE: [Gluster-users] Scaling Gluster<br>
><br>
> On Mon, 23 May 2011 at 9:55am, Anthony J. Biacco wrote<br>
><br>
> > I think i read somewhere the server in the mount string is only used to<br>
> retrieve the cluster config. So as long as that server is up at time of mount,<br>
> you're fine.<br>
> > If the server goes down after mount, it doesnt matter as the cluster config<br>
> on the mounting servers knows about all gluster servers.<br>
> > Somebody correct me if i'm wrong.<br>
><br>
> That's correct -- it's the mount-time failure that ucarp can help avoid.<br>
><br>
> > Personally, i copy the cluster config to all my mounting servers and use<br>
> > that file in the mount command instead of a gluster server hostname.<br>
><br>
> But then you lose the ability to easily and automatically distribute<br>
> configuration changes made via the 'gluster' command on the servers. I'm<br>
> not saying that can't be worked around, but everything is a tradeoff.<br>
><br>
> --<br>
> Joshua Baker-LePain<br>
> QB3 Shared Cluster Sysadmin<br>
> UCSF<br>
<br>
</div></div></blockquote></div><br>