<p dir="ltr">Il 12 nov 2016 12:53, "Kevin Lemonnier" <<a href="mailto:lemonnierk@ulrar.net">lemonnierk@ulrar.net</a>> ha scritto:<br>
> Sure, but thinking about it later we realised that it might be for the better.<br>
> I believe when sharding is enabled the shards will be dispersed across all the<br>
> replica sets, making it that losing a replica set will kill all your VMs.<br>
><br>
> Imagine a 16x3 volume for example, losing 2 bricks could bring the whole thing<br>
> down if they happen to be in the same replica set. (I might be wrong about the<br>
> way gluster disperse shards, it's my understanding only, never had the chance<br>
> to test it).<br>
> With multiple small clusters, we have the same disk space in the end but not<br>
> that problem, it's a bit more annoying to manage but for now that's allright.<br></p>
<p dir="ltr">I don't use EC because i really love the "gluster feature" to have plain files stored and not encoded in any way.</p>
<p dir="ltr">> Not really shocked there. Guess the cli should warn you when you try re-setting<br>
> the option though, that would be nice.</p>
<p dir="ltr">Exactly. I've proposed a warning in the cli when changing the shard size but this is still unfixed and this is scaring me<br>
it's a critical bug, IMHO, and should be addressed asap or any user could destroy the whole cluster with a simple command and no warning at all.</p>