At 09:28 AM 12/9/2008, Stas Oskin wrote: >Hi. > >Thanks for the example, but how actually server-side AFR works? > >I mean, when you put a file on one server, it writes to the second >one? And vice-versa? yes. client 1 updates file on server 1. server 1 and server 2 (if AFR'ed) communicate and server 1 pushes file to server 2. Client 1 reads file from server 1. Server 1 and server 2 coordinate to see if they are already in sync. if so, server 1 sends file to client 1. if not server 1 gets newer version first then send to client 1. >Regards. > >here's my server configs: > >volume home1 > type storage/posix # POSIX FS translator > option directory /gluster/home # Export this directory >end-volume > >volume posix-locks-home1 > type features/posix-locks > option mandatory on > subvolumes home1 >end-volume > >## Reference volume "home2" from remote server >volume home2 > type protocol/client # POSIX FS translator > option transport-type tcp/client > option remote-host <http://192.168.2.2>192.168.2.2 # IP > address of remote host > option remote-subvolume posix-locks-home1 # use home1 on remote host > option transport-timeout 10 >end-volume > >### Create automatic file replication >volume home > type cluster/afr > option read-subvolume posix-locks-home1 > subvolumes posix-locks-home1 home2 >end-volume > >### Add network serving capability to above home. >volume server > type protocol/server > option transport-type tcp/server # For TCP/IP transport > subvolumes posix-locks-home1 > option auth.addr.posix-locks-home1.allow > <http://192.168.2.2>192.168.2.2,<http://127.0.0.1>127.0.0.1 > > >###I believe the following will do what you want, it's not exactly >the same as mine since I added the auth option for the clients >(192.168.1.x) to mount home--the AFR volume > option auth.addr.home.allow > <http://92.168.1.1>92.168.1.1,<http://192.168.1.2>192.168.1.2,<http://127.0.0.1>127.0.0.1 > # >end-volume > >
