<html><head></head><body>Which means, of course, no redundancy until that self heal is completed. <br>
<br>
Furthermore, "replace-brick start" stopped working at all some versions ago so the removal of start and stop may as well just happen.<br><br><div class="gmail_quote">On October 30, 2014 12:41:17 AM PDT, Kaushal M <kshlmster@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">'replace-brick commit force' is still going to be available. It's just<br />that data-migration for replace-brick is going to be removed. So<br />'replace-brick (start|stop)' are going to be deprecated.<br /><br />To replace a brick in a replica set, you'll need to do a<br />'replace-brick commit force'. Self-healing will take care of filling<br />the new brick with data.<br /><br />~kaushal<br /><br />On Thu, Oct 30, 2014 at 12:56 PM, B.K.Raghuram <bkrram@gmail.com> wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> I just wanted to check if gluster replace brick commit force is "officially"<br /> deprecated in 3.6? Is there any other way to do a planned replace of just<br /> one of the bricks in a replica pair? Add/remove brick requires that new<br /> bricks be added in replica count multiples which may not be always<br /> available..<br /><br /> Thanks,<br /> -Ram<br /><br
/><hr /><br /> Gluster-devel mailing list<br /> Gluster-devel@gluster.org<br /> <a href="http://supercolony.gluster.org/mailman/listinfo/gluster-devel">http://supercolony.gluster.org/mailman/listinfo/gluster-devel</a></blockquote><br /><hr /><br />Gluster-devel mailing list<br />Gluster-devel@gluster.org<br /><a href="http://supercolony.gluster.org/mailman/listinfo/gluster-devel">http://supercolony.gluster.org/mailman/listinfo/gluster-devel</a><br /></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>