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 mattaimonetti@gmail.com
 designates 209.85.211.199 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=sE842QhNBok1bVA6vod0Up+D50P+QOLRVKz9EhvdEucr2oyl6C0X3YXEwrOPcMCBF0
         c3KgiRHBGeSBXp9lN3+GTm0zVzAKYg+F5Mmrb1Ei0mw/R7/9lhI62iTO24fYGeEGXBt0
         aQQT1AMcDEtVE4q7RVNKV9MbYPu9Y7BvLX5Js=
MIME-Version: 1.0
In-Reply-To: <b7cd8ed10909201006h6698a805wda765e346508c7b3@mail.gmail.com>
References: <b7cd8ed10909201006h6698a805wda765e346508c7b3@mail.gmail.com>
Date: Sun, 20 Sep 2009 12:55:23 -0700
Message-ID: <20fefa50909201255q56a3c665qabbac981d66a3a73@mail.gmail.com>
Subject: Re: continuous replication questions
From: Matt Aimonetti <mattaimonetti@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=00151747948ced7e7b047407be62

--00151747948ced7e7b047407be62
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Benoit, just out of curiosity, can you explain how you setup the 1000
continuous replications?

Thanks,

- Matt

On Sun, Sep 20, 2009 at 10:06 AM, Benoit Chesneau <bchesneau@gmail.com>wrot=
e:

> Hi,
>
> I've done today some tests with replications (currently 1000 continous
> replications open). From a remote node to another. So I have 1000 http
> connections opened from one node to another. Seem to work well.
>
> But I wonder what happened if one replication link hangs. Is there a
> way to know a database isn't anymore replicated except by parsing
> status ? Could we retrieve the lists of running replications maybe not
> by HTTP but with Erlang ? Would be useful since such thing could
> happened on so many open connections.
>
> About that I think we need a way to replicate in real time a full
> couchdb node to another in one http connection, it will cost less
> memory (actually 193M are used for 1000 connections) and less open
> files. I don't know if it's possible by just using the current update
> events ? Or maybe by doing something like stats by adding a function ?
> For global replication I think that only having db informations in the
> feed is enough, so we get the last updated seq and if the db changed.
> Then replicator, could get the list of changes since the last updated
> seq it stored. What do you think about it ?
>
> - beno=C3=AEt
>

--00151747948ced7e7b047407be62--