2009/8/1 Amar Tumballi <span dir="ltr"><<a href="mailto:amar@gluster.com">amar@gluster.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
'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><font color="#888888">-Amar</font></div><div><div></div><div class="h5"><div><br></div>
</div></div></blockquote></div>there are two qeustions:<br>(1) what's the functionality of "cluster/unify" in current release? in my opinion, "cluster/unify" is a translator for scaling, and now it doesn't function like that. is it right?<br>
<br>(2) whether will "gluster/unify" still exist in the future release? and could i suppose that the centralized namespace needed by "cluster/unify" is something that functions like metadata in current release?<br>
<br>on page 5 of the technical presentation (<a href="http://ftp.zresearch.com/pub/gluster/glusterfs/talks/Z/GlusterFS.pdf">http://ftp.zresearch.com/pub/gluster/glusterfs/talks/Z/GlusterFS.pdf</a>) ,there is a "unify" block on client side. so im gussing that "unify" is a essential component of client, with its namespace volume, shared by all clients, instead of metadata which traditional cluster filesystems keep, like Lustre.<br>
<br>do you agree with me ?<br><br>