[Gluster-users] Scaling Gluster

[José Celano]

Other solution I have been thinking in is making a script that before
mounting the volume
in the client side makes a previous test (perhaps ping or even the same
mount command)
and if this test fails It just tries it with the next Gluster server in the
list. The problem here
is to obtain the dynamic list of all gluster severs. I am using
sclar.netand they do that job for
me. There is a directory in every instance where they automatically put all
active server IPs for every rol.

But I am finding a simpler solution because I thought it is strange
thatGluster don´t have
a way of doing this internally. Perhaps It could be done adding a gluster
mount command with 2 o 3
"master servers" location parameters and that it chooses internally the
first is not down (like DNS).


On Mon, May 23, 2011 at 5:15 PM, Anthony J. Biacco <
abiacco at formatdynamics.com> wrote:

> 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.
> But I'm sure many others have more complicated and ever changing setups
> than me.
>
> -Tony
> ---------------------------
> Manager, IT Operations
> Format Dynamics, Inc.
> P: 303-228-7327
> F: 303-228-7305
> abiacco at formatdynamics.com
> http://www.formatdynamics.com
>
>
> > -----Original Message-----
> > From: Joshua Baker-LePain [mailto:jlb17 at duke.edu]
> > Sent: Monday, May 23, 2011 10:02 AM
> > To: Anthony J. Biacco
> > Cc: José Celano; gluster-users at gluster.org
> > Subject: RE: [Gluster-users] Scaling Gluster
> >
> > On Mon, 23 May 2011 at 9:55am, Anthony J. Biacco 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.
> > > If the server goes down after mount, it doesnt matter as the cluster
> config
> > on the mounting servers knows about all gluster servers.
> > > Somebody correct me if i'm wrong.
> >
> > That's correct -- it's the mount-time failure that ucarp can help avoid.
> >
> > > 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.
> >
> > But then you lose the ability to easily and automatically distribute
> > configuration changes made via the 'gluster' command on the servers.  I'm
> > not saying that can't be worked around, but everything is a tradeoff.
> >
> > --
> > Joshua Baker-LePain
> > QB3 Shared Cluster Sysadmin
> > UCSF
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20110523/b1279dbd/attachment.html>