Makes sense. On Thu, 16 Mar 2017 at 06:51, Raghavendra Talur <[email protected]> wrote:
> Hi, > > In the last few releases, we have changed replace-brick command such > that it can be called only with "commit force" option. When invoked, > this is what happens to the volume: > > a. distribute only volume: the given brick is replaced with a empty > brick with 100% probability of data loss. > b. distribute-replicate: the given brick is replaced with a empty > brick and self heal is triggered. If admin is wise enough to monitor > self heal status before another replace-brick command, data is safe. > c. distribute-disperse: same as above in distribute-replicate > > My proposal is to fully deprecate replace-brick command for > "distribute only" volumes. It should print out a error "The right way > to replace brick for distribute only volume is to add brick, wait for > rebalance to complete and remove brick" and return a "-1". > > Thoughts? > > Thanks, > Raghavendra Talur > _______________________________________________ > Gluster-users mailing list > [email protected] > http://lists.gluster.org/mailman/listinfo/gluster-users > -- --Atin
_______________________________________________ Gluster-users mailing list [email protected] http://lists.gluster.org/mailman/listinfo/gluster-users
