[Gluster-users] data corruption - any update?
nbalacha at redhat.com
Thu Oct 12 03:37:01 UTC 2017
On 11 October 2017 at 22:21, <lemonnierk at ulrar.net> wrote:
> > 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.
Or remove a replica set. An add-brick will not trigger a rebalance - that
needs to be done explicitly. However, a remove-brick will start the
> Gluster-users mailing list
> Gluster-users at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users