<div dir="ltr"><div><div>Hi,<br><br></div>Just curious, are you seeing poor heal performance of VMs by any chance in 3.7.9 *even* with sharding?<br><br></div>-Krutika<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 14, 2016 at 3:14 PM, Pranith Kumar Karampuri <span dir="ltr"><<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On 04/14/2016 09:46 AM, Lindsay Mathieson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sorry to bring this up again, but I never did figure out the right<br>
settings for this.<br>
<br>
If I reboot a gluster node for a rep 3 volume, what are the settings<br>
for maximising heal speed, assuming ones not worried about i/o or cpu<br>
<br>
Gluster 3.7.9<br>
Sharded volume (4MB)<br>
</blockquote></span>
The only benefit you get over replicate volumes without sharding is that only the shards which changed when the brick rebooted are healed instead of whole VM image. Apart from that I don't see any settings that will improve heal speed. You wait for 3.7.12. We are almost done backporting multi-threaded self-heal. I am in the process of writing a blog-post to give full idea about this one.<br>
<br>
Pranith<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
thanks,<br>
<br>
</blockquote><div class="HOEnZb"><div class="h5">
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">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>
</div></div></blockquote></div><br></div>