'replace-brick commit force' is still going to be available. It's just that data-migration for replace-brick is going to be removed. So 'replace-brick (start|stop)' are going to be deprecated. To replace a brick in a replica set, you'll need to do a 'replace-brick commit force'. Self-healing will take care of filling the new brick with data. ~kaushal On Thu, Oct 30, 2014 at 12:56 PM, B.K.Raghuram <bkrram@xxxxxxxxx> wrote: > I just wanted to check if gluster replace brick commit force is "officially" > deprecated in 3.6? Is there any other way to do a planned replace of just > one of the bricks in a replica pair? Add/remove brick requires that new > bricks be added in replica count multiples which may not be always > available.. > > Thanks, > -Ram > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
