|
Hi,
We had issues with data corruption before but, with glusterfs 3.8.12 we tested expanding a sharded volume and it worked fine without issues.
Try expanding a test volume and see the results yourself, for me, it was 100% reproducible.
--
Respectfully Mahdi A. Mahdi From: gluster-users-bounces@xxxxxxxxxxx <gluster-users-bounces@xxxxxxxxxxx> on behalf of lemonnierk@xxxxxxxxx <lemonnierk@xxxxxxxxx>
Sent: Wednesday, October 11, 2017 7:51 PM To: gluster-users@xxxxxxxxxxx Subject: Re: data corruption - any update? > corruption happens only in this cases:
> > - volume with shard enabled > AND > - rebalance operation > I believe so > So, what If I have to replace a failed brick/disks ? Will this trigger > a rebalance and then corruption? > > rebalance, is only needed when you have to expend a volume, ie by > adding more bricks ? That's correct, replacing a brick shouldn't cause corruption, I've done it a few times without any problems. As long as you don't expand the cluster, you are fine. Basically you can add or remove replicas all you want, but you can't add new replica sets. |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
