'cluster/distribute' is just a symlink to 'cluster/dht', which works on different design internally compared to 'cluster/unify' which needs a centralized 'namespace' volume to work. We have noticed that the 'scaling' is not possible with 'cluster/unify' and have decided to not continue any more development on cluster/unify design, instead any more enhancement of glusterfs will happen only on 'cluster/distribute' translator.<div>
<br>-Amar</div><div><br><div class="gmail_quote">On Fri, Jul 31, 2009 at 6:32 PM, Yi Ling <span dir="ltr"><<a href="http://lingyi.pro">lingyi.pro</a>@<a href="http://gmail.com">gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><br><div class="gmail_quote">2009/8/1 Amar Tumballi <span dir="ltr"><<a href="mailto:amar@gluster.com" target="_blank">amar@gluster.com</a>></span><div class="im"><br><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
Any reason to go with 'cluster/unify' instead of 'cluster/distribute'? Other than for 'switch' scheduler, we recommend 'cluster/distribute' for combining the storage. <div><div></div><div>
<div><br></div></div></div></blockquote></div></div><br>so pls tell the difference between 'cluster/unify' and 'cluster/distribute' ?<br><br>is 'cluster/unify' a essential translator on client?<br>
<br>and the difference between 'cluster/distribute' and 'cluster/dht' ?<br>
<br>so many similar translators that im very puzzled...<br>
</blockquote></div><br></div>