[Gluster-users] New to GlusterFS

[John Mark Walker]

Hi JC,

Yes, the default is a 42-second timeout for failover. You can configure
that to be a smaller window.

-JM
 On Oct 22, 2013 10:57 AM, "JC Putter" <jcputter at gmail.com> wrote:

> Hi,
>
> I am new to GlusterFS, i am trying to accomplish something which i am
> not 100% sure is the correct use case but hear me out.
>
> I want to use GlusterFS to host KVM VM's, from what I've read this was
> not recommended due to poor write performance however since
> libgfapi/qemu 1.3  this is now viable ?
>
>
> Currently i'am testing out GlusterFS with two nodes, both running as
> server and client
>
> i have the following Volume:
>
> Volume Name: DATA
> Type: Replicate
> Volume ID: eaa7746b-a1c1-4959-ad7d-743ac519f86a
> Status: Started
> Number of Bricks: 1 x 2 = 2
> Transport-type: tcp
> Bricks:
> Brick1: glusterfs1.example.com:/data
> Brick2: glusterfs2.example.com:/data
>
>
> and mounting the brick locally on each server as /mnt/gluster,
> replication works and everything but as soon as i kill one node, the
> directory /mnt/gluster/ becomes unavailable for 30/40 seconds
>
> log shows
>
> [2013-10-22 11:55:48.055571] W [socket.c:514:__socket_rwv]
> 0-DATA-client-0: readv failed (No data available)
>
>
> Thanks in advance!
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131022/56b29214/attachment.html>