Hi Antonio, Client side unify is simple and easier approach in my opinion. But depending on how your i/o pattern is, how your network topology is, you may want to change it. but to start with, unify on client side is a better approach.
Regards, Amar On Wed, Apr 9, 2008 at 1:41 AM, Antonio González < [EMAIL PROTECTED]> wrote: > Hello all, > > > > I try to think about a GlusterFS file system, where we have a lot of > servers > and clients. In my firsts test I place the unify translator in a central > server, because I think that is more scalable that a schema where the > unify > translator were in the client, because it would necessary that the clients > knows the bricks exported in the full system. > > > > What schema is better, a central unify or a unify client…?? > > > > > > _______________________________________________ > Gluster-devel mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/gluster-devel > -- Amar Tumballi Gluster/GlusterFS Hacker [bulde on #gluster/irc.gnu.org] http://www.zresearch.com - Commoditizing Supercomputing and Superstorage!
_______________________________________________ Gluster-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/gluster-devel
