Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com
 designates 209.85.212.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <996688918.45063.1313760721103.JavaMail.root@unx-s-manc3>
References: <996688918.45063.1313760721103.JavaMail.root@unx-s-manc3>
From: Paul Davis <paul.joseph.davis@gmail.com>
Date: Fri, 19 Aug 2011 12:26:41 -0500
Message-ID: 
 <CAJ_m3YCstMMqcSyY3oNhqkBqzUY+F4QfnoU6JnUYAeRkjpcPUQ@mail.gmail.com>
Subject: Re: Multi node topology
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Robert,

There are two projects for running CouchDB in a cluster:
CouchDB-Lounge and BigCouch. CouchDB-Lounge is a combination of an
nginx module and Python proxy that handles managing multiple backend
CouchDB nodes. BigCouch is a pure Erlang implementation that works
more like Dynamo.

[1] http://tilgovi.github.com/couchdb-lounge/
[2] http://github.com/cloudant/bigcouch

On Fri, Aug 19, 2011 at 8:32 AM, Robert Elliot <rob@lidalia.org.uk> wrote:
> Hi,
>
> We are considering setting up a cluster with more than two nodes. There i=
s a lot of documentation regarding two nodes but we couldn't find an exact =
answer for let's say a cluster of 4 nodes.
>
> Would you recommend a multi-master setup where all nodes receive writes? =
=A0This would be simpler to setup and administer, and would also be the mos=
t fault tolerant (any combination of nodes can be shutdown so long as one i=
s still active).
>
> If so, should we use only push replication? =A0Or only pull replication? =
=A0Or a combination of both?
>
> Assuming we are using pull replication within 4 nodes: A, B, C and D. Sho=
uld we set up A to pull changes from B, C and D, B to pull changes from A, =
C and D, C to pull changes from A, B and D and D to pull changes from A, B =
and C? Is this the recommended approach?
>
> Thanks for any guidance,
>
> Rob
>