thanks, looks good. I have one thought, that might be worthy of discussion: Personally I prefer server side AFR, because I don't want a mis-configured client to cause problems with replication. However, it seems the current only way to get high-availability to the client is for the client to run AFR so that if one server fails you still have access. so, having afr onthe servers AND the clients seems like it might just add weird overhead? would it even work well at all? and so I'm thinking, server side AFR is better and so there might be nice to have a multi-server translator or something where you can specify multiple servers and an access policy (like with unify-- rr, lru, etc.) to address the availability issue.?? At 10:47 PM 12/17/2008, you wrote: >2008/12/18 Keith Freedman <freedman at freeformit.com>: > > I've unpacked the rc4 distribution from > > http://ftp.gluster.com/pub/gluster/glusterfs/1.4/ , there is no afr.pdf in > > the doc folder > >Thanks for spotting. I had forgot to include it in the distribution >tarball. I've made the necessary changes and it will go out with >future releases. Until then please get it from either the repository >or > >http://gnu.zresearch.com/~vikas/afr.pdf > >Vikas >-- >Engineer - Z Research >http://gluster.com/
