Monitor replicated Gluster setup ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On Thu, Jul 12, 2012 at 07:38:18AM +0000, Stefan Schloesser wrote:
> > > To switch IP for what? glusterfs in replicated mode, using the
> > > native
> > > (FUSE) client, doesn't need this.  The client talks to both
> > > backends, and if either backend fails, it continues to work.
> > [>]
> > I am slightly confused here, I don't have a client (at least in the
> > sense of a different machine), it's only 2 servers with each running
> > an apache which uses the Filesystem (simply mounted).
> 
> You mean Apache is reading the glusterfs bricks locally? That's wrong; any
> writes would screw up replication.  You should mount the glusterfs volume
> via a FUSE mount, and have Apache access files through that mountpoint.
> That's what I mean by a "client".  The fact it happens to be on the same
> server as where one of the glusterfs storage bricks runs is irrelevant.
> 
I am mounting it via 
mount -t glusterfs -o log-level=WARNING,log-file=/var/log/gluster.log cluster-1:/shared /shared

and sure, the apache will write to it ..
I hope that's ok?

Stefan



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux