Furthermore, "replace-brick start" stopped working at all some versions ago so the removal of start and stop may as well just happen.
On October 30, 2014 12:41:17 AM PDT, Kaushal M <kshlmster@xxxxxxxxx> wrote:
'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-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
