<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 12, 2016 at 4:06 PM, Gandalf Corvotempesta <span dir="ltr"><<a href="mailto:gandalf.corvotempesta@gmail.com" target="_blank">gandalf.corvotempesta@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">2016-07-12 12:34 GMT+02:00 Pranith Kumar Karampuri <<a href="mailto:pkarampu@redhat.com">pkarampu@redhat.com</a>>:<br>
> If you add 6 new disks to the cluster by bringing in a new node with replica<br>
> count 3 you are essentially are adding 2 replica sets. Since you can't have<br>
> replica sets with bricks from same node, we need to get empty bricks from<br>
> other nodes which require replace-brick operation.<br>
<br>
</span>If I replace existing bricks, i'm not adding free space but only move<br>
data around.<br>
</blockquote></div>True. But at the end of 4 replace-bricks, you have 4 bricks from earlier configuration which are empty now, which can be re-used. So essentially you have 6 empty bricks which can be put back into use, but these can be used to form replica sets as they are not from same machine. So you add-brick 2 replica sets with these 6 bricks and do rebalance. Makes sense?<br></div><div class="gmail_extra"><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>