[Gluster-users] 3.7.16 with sharding corrupts VMDK files when adding and removing bricks

Gandalf Corvotempesta gandalf.corvotempesta at gmail.com
Sat Nov 12 16:40:55 UTC 2016

2016-11-12 10:21 GMT+01:00 Kevin Lemonnier <lemonnierk at ulrar.net>:
> We've had a lot of problems in the past, but at least for us 3.7.12 (and 3.7.15)
> seems to be working pretty well as long as you don't add bricks. We started doing
> multiple little clusters and abandonned the idea of one big cluster, had no
> issues since :)

I was thinking about this.
If you meant creating multiple volumes, ok, but having to create
multiple clusters is a bad idea.
Gluster performs better with multiple nodes, if you have to split the
infrastructure (and nodes)
in multiple cluster, you'll affect the performance.

Is something like to create multiple enterprise SAN to avoid data corruption.
Data corruption must be address with firmware/software updates, not by
creating multiple storages.

if you create 2 gluster storages, you'll get the same issues in
multiple storages. It's a bad workaround, not a solution.

More information about the Gluster-users mailing list