<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 12, 2016 at 8:24 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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">2016-07-12 14:06 GMT+02:00 Anuradha Talur <<a href="mailto:atalur@redhat.com">atalur@redhat.com</a>>:<br>
> I realize I just repeated the same example in different words but I hope this answers<br>
> your questions. So do let us know if something is not clear.<br>
<br>
</span>Is unclear, probably because i don't understand how gluster works and<br>
because I don't<br>
understand why was designed like this. Having to replace bricks just<br>
to add a single<br>
server and not multiple servers due to the replica count, is absolutely unclear. <br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Any other scale-out storage allows this natively.<br>
</blockquote></div>Generally most of these systems have a dedicated metadata server where for each file they store on which servers(replicas) the file is stored. In gluster there is no metadata server, while it gives flexibility in some other ways, In this aspect it becomes a bit rigid. The steps I gave above eventually achieve the same thing. Another way to solve this problem is to flip the order of replication and distribution layers but that will need a lot of subsystems to be tested thoroughly.<br><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>