[Gluster-users] simple AFR setup, one server crashes, entire cluster becomes unusable ?

[Stas Oskin]

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?

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 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 192.168.2.2,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 92.168.1.1,192.168.1.2,127.0.0.1 #
> end-volume
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20081209/599f3c3e/attachment.html>