<div dir="ltr">Any reason you can't just set network.ping-timeout to a very large number?</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 1, 2014 at 1:08 AM, Franco Broi <span dir="ltr"><<a href="mailto:franco.broi@iongeo.com" target="_blank">franco.broi@iongeo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Wed, 2014-04-30 at 21:29 +0200, Michal Pazdera wrote:<br>
> What we would like to achieve is the same behavior as NFS or Lustre<br>
> does<br>
> where running client jobs hang until<br>
> the target is back online and then continues in the job.<br>
<br>
</div>This is what we would like too.<br>
<br>
I think it's reasonable for a job that is in the process of writing a<br>
file on a brick that disappears to fail but interrupted reads should be<br>
recoverable.<br>
<div class="HOEnZb"><div class="h5"><br>
<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Justin Dossey<br>CTO, PodOmatic<div><br></div>
</div>