<div dir="ltr">yes it's configurable with:<div><br></div><div>network.ping-timeout<br></div><div><br></div><div>and default is 42 seconds I believe.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 22 May 2016 at 03:39, Kevin Lemonnier <span dir="ltr"><<a href="mailto:lemonnierk@ulrar.net" target="_blank">lemonnierk@ulrar.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Let's assume 10.000 shard on a server being healed.<br>
> Gluster heal 1 shard at once, so the other 9.999 pieces would be read<br>
> from the other servers<br>
> to keep VM running ? If yes, this is good. If not, in this case, the<br>
> whole VM need to be healed<br>
> and thus, the whole VM would hangs<br>
<br>
</span>Yes, that seems to be what's hapenning on 3.7.11.<br>
Couldn't notice any freez during heals, except for a brief one when<br>
a node just went down : looks like gluster hangs for a few seconds<br>
while waiting for the node before deciding to mark it down and continue<br>
without it.<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Kevin Lemonnier<br>
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111<br>
</div></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><br></div>