<p dir="ltr">Il 12 nov 2016 10:21, "Kevin Lemonnier" <<a href="mailto:lemonnierk@ulrar.net">lemonnierk@ulrar.net</a>> ha scritto:<br>
> We've had a lot of problems in the past, but at least for us 3.7.12 (and 3.7.15)<br>
> seems to be working pretty well as long as you don't add bricks. We started doing<br>
> multiple little clusters and abandonned the idea of one big cluster, had no<br>
> issues since :)<br>
></p>
<p dir="ltr">Well, adding bricks could be usefull... :)</p>
<p dir="ltr">Having to create multiple cluster is not a solution and is much more expansive.<br>
And if you corrupt data from a single cluster you still have issues</p>
<p dir="ltr">I think would be better to add less features and focus more to stability.<br>
In a software defined storage, stability and consistency are the most important things</p>
<p dir="ltr">I'm also subscribed to moosefs and lizardfs mailing list and I don't recall any single data corruption/data loss event</p>
<p dir="ltr">In gluster, after some days of testing I've found a huge data corruption issue that is still unfixed on bugzilla.<br>
If you change the shard size on a populated cluster, you break all existing data.<br>
Try to do this on a cluster with working VMs and see what happens....<br>
a single cli command break everything and is still unfixed.</p>