[Gluster-users] AFR with re-mount option

Anush Shetty anush at gluster.com
Tue Feb 23 04:06:18 UTC 2010


I see that you have used replicate on the  server-side. It would work
if you can setup replicate on the client-side.

-
Anush

On Tue, Feb 23, 2010 at 8:59 AM, Frederico Madeira <fmadeira at gmail.com> wrote:
> Follow Bellow:
>
> ###### Server1:
> volume posix
>   type storage/posix
>   option directory /opt/data/export
> end-volume
> volume brick1
>  type features/posix-locks
>  subvolumes posix
> end-volume
> volume brick2
>   type protocol/client
>   option transport-type tcp/client
>   option remote-host 192.168.15.37   # IP address of server2
>   option remote-subvolume brick1   # use brick1 on server2
> end-volume
>
> volume replicate
>   type cluster/replicate
>   subvolumes brick1 brick2
> end-volume
>
> volume server
>   type protocol/server
>   option transport-type tcp/server
>   subvolumes replicate
>   option auth.ip.brick1.allow 192.168.15*,127.0.0.1
>   option auth.ip.replicate.allow 192.168.15*,127.0.0.1
>   option auth.ip.server.allow 192.168.15*,127.0.0.1
> end-volume
>
>
> ######## Server2:
>
> volume posix
>   type storage/posix
>   option directory /opt/data/export
> end-volume
> volume brick1
>  type features/posix-locks
>  subvolumes posix
> end-volume
>
> volume brick2
>   type protocol/client
>   option transport-type tcp/client
>   option remote-host 192.168.15.40   # IP address of server2
>   option remote-subvolume brick1   # use brick1 on server2
> end-volume
>
> volume replicate
>   type cluster/replicate
>   subvolumes brick1 brick2
> end-volume
>
> volume server
>   type protocol/server
>   option transport-type tcp/server
>   subvolumes replicate
>   option auth.ip.brick1.allow 192.168.15*,127.0.0.1
>   option auth.ip.replicate.allow 192.168.15*,127.0.0.1
> end-volume
>
> ##### Client1
> volume brick
>   type protocol/client
>   option transport-type tcp/client # for TCP/IP transport
>   option remote-host 192.168.15.40   # IP address of the server
>   option remote-subvolume server      # name of the remote volume
> end-volume
>
>
> ##### Client2
> volume brick
>   type protocol/client
>   option transport-type tcp/client # for TCP/IP transport
>   option remote-host 192.168.15.37   # IP address of the server
>   option remote-subvolume server      # name of the remote volume
> end-volume
>
>
> Fred,
>
>
>
>
> 2010/2/22 Anush Shetty <anush at gluster.com>:
>> On Tue, Feb 23, 2010 at 7:49 AM, Frederico Madeira <fmadeira at gmail.com> wrote:
>>> Mount -t glusterfs /etc/glusterfs/glusterfs.vol /media/Storage
>>>
>>
>> Frederico, when server1 fails, you processes on the client shouldn't
>> be failing. And all the data on the client will be from the server2.
>> Can you attach your vol files here? Also tell us which version of
>> GlusterFS you are using for this setup.
>>
>> -
>> Anush
>>
>
>
>
> --
> Frederico Madeira
> fmadeira at gmail.com
> www.madeira.eng.br
>



-- 
Anush,
http://gluster.com



More information about the Gluster-users mailing list