<br><div class="gmail_quote">On Tue, Jan 10, 2012 at 15:11, Jeff White <span dir="ltr"><<a href="mailto:jaw171@pitt.edu">jaw171@pitt.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div bgcolor="#ffffff" text="#000000"><div class="im">
On 01/10/2012 03:25 AM, Carl Boberg wrote:
<blockquote type="cite">Hello,
<div><br>
</div>
<div>I have started evaluating GlusterFS for our application to
share data and everything seems very satisfactory so far :)</div>
<div>I only have a few questions that are about the timeout that
happens when one of the servers goes down.</div>
<div><br>
</div>
<div>We have a simple 2 server setup with 2 replicated volumes. </div>
</blockquote></div>
You should post what version you are using and the output of
'gluster volume info'.<div class="im"><br></div></div></blockquote><div><br></div><div>My rookie misstake :)</div><div><br></div><div><div>Volume Name: dev-msg-vol</div><div>Type: Replicate</div><div>Status: Started</div>
<div>Number of Bricks: 2</div><div>Transport-type: tcp</div><div>Bricks:</div><div>Brick1: gfs1:/glusterfs/dev-msg-vol/exp1</div><div>Brick2: gfs2:/glusterfs/dev-msg-vol/exp2</div></div><div><br></div><div><div>Volume Name: dev-attach-vol</div>
<div>Type: Replicate</div><div>Status: Started</div><div>Number of Bricks: 2</div><div>Transport-type: tcp</div><div>Bricks:</div><div>Brick1: gfs1:/glusterfs/dev-attach-vol/exp1</div><div>Brick2: gfs2:/glusterfs/dev-attach-vol/exp2</div>
</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#ffffff" text="#000000"><div class="im">
<blockquote type="cite">
<div>About 10 clients connecting to both of the volumes and
filesizes range around a few bytes to about a coupple of megs.
Its a lot of files and folders... <br>
</div>
</blockquote></div>
Define 'a lot'. I'm soon going to migrate 83 million files to
Gluster and that's not 'a lot' compared to some others.<div class="im"><br></div></div></blockquote><div><br></div><div>Sorry about that. We apparently dont have that many files then :) About a couple of million, thats all.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#ffffff" text="#000000"><div class="im">
<blockquote type="cite">
<div>When one of the servers goes down all clients seems to hang
for about 40-50 seconds before being able to access files and
folders again. Write operations continues during this but i
guess it is being done in memory until the file is accessible
again..</div>
<div>What controles this timeout? Is it possible to adjust it? Is
it advisable to adjust it, if you can?<br clear="all">
</div>
</blockquote></div>
This might be what you are looking for but I don't know if it's
advisable to change it.<br>
<br>
<a href="http://www.gluster.org/community/documentation/index.php/Gluster_3.2:_Setting_Volume_Options#network.ping-timeout" target="_blank">http://www.gluster.org/community/documentation/index.php/Gluster_3.2:_Setting_Volume_Options#network.ping-timeout</a><div class="im">
<br></div></div></blockquote><div><br></div><div><div>Ah. Should have seen that when I was going through the documentation.... Still it does not say anything about the effects of changing the timeout? It says it is an "expensive" operation but why is 42 seconds the agreed timeout? And how expensive? Expensive in what terms, cpu, i/o, network?</div>
<div>Im not expecting an answer for this but it is interesting to note that this is an important setting concerning uptime functionallity during a server failure in a replicated setup. If i have an intense read/write application working on a gluster volume id be very interested in having this as short as possible. As such I just wish there were more information regarding this setting.</div>
</div><div><br></div><div>Thank you for the pointer to the documentation ( I should have found it for myself ...) </div><div><br></div><div>Cheers</div></div>