From user-return-15665-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Wed Apr 06 15:17:13 2011 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 49684 invoked from network); 6 Apr 2011 15:17:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Apr 2011 15:17:13 -0000 Received: (qmail 41837 invoked by uid 500); 6 Apr 2011 15:17:11 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 41741 invoked by uid 500); 6 Apr 2011 15:17:11 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 41733 invoked by uid 99); 6 Apr 2011 15:17:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2011 15:17:11 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=FREEMAIL_FROM,FS_REPLICA,MIME_QP_LONG_LINE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nebupookins@gmail.com designates 209.85.216.52 as permitted sender) Received: from [209.85.216.52] (HELO mail-qw0-f52.google.com) (209.85.216.52) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2011 15:17:03 +0000 Received: by qwb8 with SMTP id 8so1474712qwb.11 for ; Wed, 06 Apr 2011 08:16:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:references:from:content-type:x-mailer :in-reply-to:message-id:date:to:content-transfer-encoding :mime-version; bh=T5k7E21tCTHxVMLgyYgCSc34yqoocvlArRuSVv70Uvg=; b=jakZBV/VXIblx1p9NFLslpkzcuFtdiCdwa7bXOBiUHlWdF88Pw6nK8240JzZTkx4hs gdNfD64etBGv99HDWeFdF70ewFaaVhu7lTVMdNzRrff/Yo1SQhZzWtBOxMdGYCvXITIw OE+PkNIYY+XEdUv/YRoJUZ2wbpSAXCDvgh0ms= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; b=JBGj853b78Xs7APnzJp8ORqx/CXxTGaM7ftz8xs6NKhbdb5SSCfrPYedQFpk5w0ROK Y+0tSLZIZe5vEFkh5qYhfR0BNmXI2cdjIjxXtwmtksz1BX8/qq3DHPVSPtie+FH9A2Ke VE+9NJSmJbmuBDmHXK3Al+VF7ig71m3rYD2yU= Received: by 10.224.18.202 with SMTP id x10mr945058qaa.285.1302103002248; Wed, 06 Apr 2011 08:16:42 -0700 (PDT) Received: from [10.232.137.155] (out-pq-252.wireless.telus.com [216.218.29.252]) by mx.google.com with ESMTPS id t17sm447647qcs.47.2011.04.06.08.16.41 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Apr 2011 08:16:41 -0700 (PDT) Subject: Re: Peer-to-Peer Replication References: From: Nebu Pookins Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (8G4) In-Reply-To: Message-Id: Date: Wed, 6 Apr 2011 11:16:18 -0400 To: "user@couchdb.apache.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (iPhone Mail 8G4) X-Virus-Checked: Checked by ClamAV on apache.org The replication model is such that for every connected graph of peers, all p= eers in that graph will update to the same up-to-date state. This is what th= ey call "eventual consistentcy".=20 It's like in bittorrent, you don't have to worry about the clients with full= copies of the file somehow losing data; the replication data is versionned,= so your peers will only replicate "forward" in time, not backwards.=20 Sent from my iPhone On 2011-04-05, at 1:36 PM, Zdravko Gligic wrote: > Hi Folks, >=20 > Are there any large implementations of CouchDB peer-to-peer > replications or even smaller open source samples? Actually, the piece > that I am mostly interested in is at the application/design end of how > to go about implementing the "traffic cop" for a use case where > everyone is eventually synchronized with everyone else. >=20 > Given a large number of peers that one could replicate to/from, is > there anything within CouchDB that can be "posted centrally" to know > how up to date anyone is, so that badly out of date peers are > replicate to/from the more up to date ones, instead to/from each > other? What else should I ask, if I knew better ;?) >=20 > Thanks, > Zdravko