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 robert.newson@gmail.com
 designates 209.85.220.227 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:content-transfer-encoding;
        b=xuzO7aZntG+eBQHPO6yGAcAFzVUd8WtKf1nRm5cuJMzf6VESdiZ0OakoaSA20IEUm0
         kWSPc6xv3uBXc+EsznQrN7/EHjbUFZAIND/uJiEKeJcNv0Xgou102Qf9+tND6yvXd1Fy
         9w11PqnlodYUTTNd8QuF7aTazNInkn4b5AqE4=
MIME-Version: 1.0
In-Reply-To: <4A9454F3.6020107@meetinghouse.net>
References: <4A94534F.9020800@orcaware.com>
 <4A9454F3.6020107@meetinghouse.net>
Date: Tue, 25 Aug 2009 22:37:44 +0100
Message-ID: <46aeb24f0908251437k1549cd4dq4f76a4a2eca8b391@mail.gmail.com>
Subject: Re: Replication and new user questions
From: Robert Newson <robert.newson@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I can only speak to the new continuous replication. After a few days
of stress testing and bug fixes from the team, it's really pretty
amazing.

b.

On Tue, Aug 25, 2009 at 10:17 PM, Miles
Fidelman<mfidelman@meetinghouse.net> wrote:
> Blair Zajac wrote:
>>
>> Hello,
>>
>> We're looking at using CouchDB's replication to allow us to easily have
>> multi-master replicating databases across multiple facilities, (e.g. Los
>> Angeles, Albuquerque, Bristol, England, etc). =A0It looks like it'll be =
the
>> perfect tool for the job.
>>
>> Some questions on the current implementation and the work that I've read
>> is going to be in forthcoming releases.
>>
>> 1) What's the most robust automatic replication mechanism? =A0While
>> continuous replication looks nice, I see there's some tickets open with =
it
>> and that it has issues with four nodes. =A0Is a more robust solution, bu=
t a
>> little slower and heavier, it to have an update_notification that manual=
ly
>> POSTs to _replicate?
>>
>> 2) With the persistent continuous replication feature, is there a way to
>> stop continuous replication without restarting couchdb? =A0Will there be=
 a way
>> to manage the list of replicant databases when the persistent continuous
>> replication feature is complete?
>>
> I'm sort of interested in this too. =A0We have an application we're devel=
oping
> that's somewhat analogous to USENET News. =A0What we want to do is:
>
> 1. define arbitrary groups, analogous to newsgroups
>
> 2. distribute control messages to a large number of nodes, allowing a nod=
e
> to subscribe (or not)
>
> 3. when a message (document) is posted (inserted) into a group, it gets
> replicated to all subscribed nodes
>
> I keep looking at CouchDB and thinking this should be perfect for what we=
're
> doing, but the details of replication are really sketchy.
>
> Miles Fidelman
>
> --
> In theory, there is no difference between theory and practice.
> In practice, there is. =A0 .... Yogi Berra
>
>
>