<div dir="ltr">I think you are confused about what sharding does. In a sharded replica 3 volume all the shards exist on all the replicas so there is no distribution. Might you be getting confused with erasure coding? The upshot of sharding is that if you have a failure, instead of healing multiple gigabyte vm files for example, you only heal the shards that have changed. This generally shortens the heal time dramatically.<div><br></div><div>Alastair</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 18 May 2016 at 12:54, Gandalf Corvotempesta <span dir="ltr"><<a href="mailto:gandalf.corvotempesta@gmail.com" target="_blank">gandalf.corvotempesta@gmail.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="">Il 18/05/2016 13:55, Kevin Lemonnier ha scritto:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes, that's why you need to use sharding. With sharding, the heal is much quicker and the whole VM isn't freezed during the heal, only the shard being healed. I'm testing that right now myself and that's almost invisible for the VM using 3.7.11. Use the latest version though, it really really wasn't transparent in 3.7.6 :).<br>
</blockquote></span>
I don't like sharding. With sharing all "files" are split in shard and distributed across the whole cluster.<br>
If everything went bad, reconstructing a file from it shards could be hard.<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>