<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 17 October 2015 at 02:51, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":4gz" class="a3s" style="overflow:hidden">You may also want to check sharding (currently in beta with 3.7) where large files are chunked to smaller fragments. With this scheme, self-healing (and rolling checksum computation thereby) happens only on those fragments that undergo changes when one of the nodes in a replicated set is offline. This has shown nice improvements in gluster's resource utilization during self-healing.<br>
</div></blockquote></div><br><br></div><div class="gmail_extra">Does it effect read speed and random i/o? I guess that would depend on the methodology used to calculate shard location for a given block. Could be quite interesting on top of zfs, love to test.<br></div><div class="gmail_extra"><br clear="all"><br>-- <br><div class="gmail_signature">Lindsay</div>
</div></div>