<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
The reason for the long (42 second) ping-timeout is because
re-establishing fd's and locks can be a very expensive operation.
Allowing a longer time to reestablish connections is logical, unless
you have servers that frequently die.<br>
<br>
If you shut down a server through the normal kill process, the TCP
connections will be closed properly. The client will be aware that
the server is going away and there will be no timeout. This allows
server maintenance without encountering that issue.<br>
<br>
One issue with a 42 second timeout is that ext4 may detect an error
and remount itself read only should that happen while the VM is
running. You can override this behavior by specifying the mount
option, "errors=continue" in fstab ("errors=remount-ro" is the
default). The default can be changed, as well, by changing the
superblock option with tune2fs.<br>
<br>
<div class="moz-cite-prefix">On 10/22/2013 03:12 AM, John Mark
Walker wrote:<br>
</div>
<blockquote
cite="mid:CAMUFnfZhcUFJM+aOW4vp5h_aC_AWUVTVUYhbXs+v_N7voAadpw@mail.gmail.com"
type="cite">
<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 moz-do-not-send="true" 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 moz-do-not-send="true"
href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a moz-do-not-send="true"
href="http://supercolony.gluster.org/mailman/listinfo/gluster-users"
target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</body>
</html>