<p>Hi JC,</p>
<p>Yes, the default is a 42-second timeout for failover. You can configure that to be a smaller window.</p>
<p>-JM<br>
</p>
<div class="gmail_quote">On Oct 22, 2013 10:57 AM, "JC Putter" <<a href="mailto:jcputter@gmail.com">jcputter@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I am new to GlusterFS, i am trying to accomplish something which i am<br>
not 100% sure is the correct use case but hear me out.<br>
<br>
I want to use GlusterFS to host KVM VM's, from what I've read this was<br>
not recommended due to poor write performance however since<br>
libgfapi/qemu 1.3 this is now viable ?<br>
<br>
<br>
Currently i'am testing out GlusterFS with two nodes, both running as<br>
server and client<br>
<br>
i have the following Volume:<br>
<br>
Volume Name: DATA<br>
Type: Replicate<br>
Volume ID: eaa7746b-a1c1-4959-ad7d-743ac519f86a<br>
Status: Started<br>
Number of Bricks: 1 x 2 = 2<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: glusterfs1.example.com:/data<br>
Brick2: glusterfs2.example.com:/data<br>
<br>
<br>
and mounting the brick locally on each server as /mnt/gluster,<br>
replication works and everything but as soon as i kill one node, the<br>
directory /mnt/gluster/ becomes unavailable for 30/40 seconds<br>
<br>
log shows<br>
<br>
[2013-10-22 11:55:48.055571] W [socket.c:514:__socket_rwv]<br>
0-DATA-client-0: readv failed (No data available)<br>
<br>
<br>
Thanks in advance!<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div>