<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 3, 2017 at 5:59 PM, <span dir="ltr"><<a href="mailto:lemonnierk@ulrar.net" target="_blank">lemonnierk@ulrar.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Fix is up @ <a href="https://review.gluster.org/#/c/17160/" rel="noreferrer" target="_blank">https://review.gluster.org/#/<wbr>c/17160/</a> . The only thing which<br>
> we'd need to decide (and are debating on) is that should we bypass this<br>
> validation with rebalance start force or not. What do others think?<br>
<br>
</span>I think that if you are specifying force, that's your business.</blockquote><div><br></div><div>+1. I say we show warning in case of no --force. handle the case similar to replace-brick --force remove-brick commit force like way.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Maybe still<br>
show a warning and ask for a yes / no confirmation after, in case some people<br>
use force "by default" ?<br></blockquote><div><br></div><div>we had kept --force as an option to script gluster CLIs so the scripts / integrations would work without depending on stdin input.<br><br></div><div>Regards,<br></div><div>Amar<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>
</div></div>