[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gluster-devel] Server-side AFR

From: gordan
Subject: [Gluster-devel] Server-side AFR
Date: Wed, 23 Apr 2008 15:44:55 +0100 (BST)
User-agent: Alpine 1.10 (LRH 962 2008-03-14)

I'm trying to do server-side AFR, and the sort of thing I'm coming up with is a bit like the following:

volume foo1
        type storage/posix
        option directory /gluster

volume foo2
        type protocol/client
        option transport-type tcp/client
        option remote-host
        option remote subvolume foo

volume foo
        type cluster/afr
        subvolumes foo1 foo2

volume server
        type protocol/server
        option transport-type tcp/server
        subvolumes foo

The only difference between the two servers is the IP address in the remote AFR block ( instead of .1).

The question I have is - would this cause a circular replication meltdown? Or are loops somehow detected/prevented/avoided? Effectively, the client would connect to one server only, and upload the data, which would get replicated to the other server, which, since it also replicates back, replicates the file back, which triggers the local server to replicate, etc, etc, etc.

What prevents this sort of thing from occuring, and is there a better way to achieve this kind of a setup?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]