<p dir="ltr">I assume that this is because the host which went down is even the host which is used for mounting client.</p>
<p dir="ltr">Suppose there are 2 host. Host1 and Host2. And client is mounted as<br>
mount -t glusterfs host1:brick1 /mnt</p>
<p dir="ltr">In this case if host1 goes down, client will wait till network ping timeout before it starts accessing volume using other host(host2).</p>
<p dir="ltr">So I think this is expected behaviour.</p>
<p dir="ltr">Thanks,<br>
Bipin Kunal</p>
<div class="gmail_quote">On Dec 7, 2015 10:57 PM, "L, Sridhar (Nokia - IN/Bangalore)" <<a href="mailto:sridhar.l@nokia.com">sridhar.l@nokia.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<font face="Calibri" size="2"><span style="font-size:11pt">
<div>Hello,</div>
<div> </div>
<div>I am running gluster storage in distributed replicated mode. When one of the brick (host) goes offline, operations on the file system by the client will hang for a while and resumes after sometime. I searched and found that operations hang for the period
set in network.ping-timeout. </div>
<div>Can anyone explain me why the client operations will hang even though the other brick is available with all the data?</div>
<div> </div>
<div><font color="#60636D"> </font></div>
<div><font face="Helvetica" size="2" color="#60636D"><span style="font-size:9pt">Regards,</span></font></div>
<div><font face="Helvetica" size="2" color="#60636D"><span style="font-size:9pt">Sridhar L</span></font></div>
<div> </div>
<div> </div>
<div> </div>
</span></font>
</div>
<br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br></blockquote></div>