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

Kevin Lemonnier lemonnierk at ulrar.net
Sat Nov 12 19:51:06 UTC 2016

>    doing so means 3 times cost, 3 times disks to add and manage and so on
>    is not "commodity"

It's the exact same cost. All the clusters have replica 3, there is absolutly
no difference in cost if they are separate or not.
It's not as easy to manage sure, but it's not like I'm tweaking the conf

>    If you have to create multiple cluster andA  not using the scale-out
>    feature why don't you use drbd or similiar?

DRBD 8 doesn't support 3 replicas, and DRBD 9 last time I tried it
was basically unusable (well, not surprising for a beta).
And on top of that, gluster heals after a network outage is transparent
and automatic, DRBD's heal are a huge pain. Since we are using OVH servers,
the network really can't be trusted unfortunatly, we do have a lot of heals

We use DRBD a lot when we need normal master / slave replication, it's great
for that, but to run VMs I really don't like it. One of our client has a
proxmox 3 cluster with DRBD 8, everytime there is a little problem with
the network it's horrible to fix, compared to gluster.

Kevin Lemonnier
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Digital signature
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20161112/10120521/attachment.sig>

More information about the Gluster-users mailing list