Hi Keith, please find the inlined comments. On Tue, Jan 27, 2009 at 3:34 PM, Keith Freedman <freedman at freeformit.com>wrote: > At 09:41 PM 1/26/2009, Raghavendra G wrote: > >namespace is just a cache, which holds the directory tree of unify. > >Please note that the files contained in this directory tree are of > >zero byte sized. > > > >what about storage scalibality in this design? both server and > >client. can you please give one example ? > > > >only bottleneck in scalability is the namespace node. It should be > >able to hold the entire directory structure of unify (with zero byte > >sized files). Other than that, a new node can be added just by > >changing the configuration file and remounting glusterfs. > > so, it would be advisable for people to use a filesystem with a very > small blocksize and a large number of inodes (or one that supports > dynamic inode allocation) presumably? yes. > > is this documented as a suggestion anywhere? Its mentioned in the following FAQ. http://gluster.org/docs/index.php/Understanding_Unify_Translator#Namespace_FAQ > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users > -- Raghavendra G -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20090127/3826072c/attachment.htm
