Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 5812 invoked from network); 20 Sep 2009 17:07:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Sep 2009 17:07:20 -0000 Received: (qmail 20884 invoked by uid 500); 20 Sep 2009 17:07:19 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 20810 invoked by uid 500); 20 Sep 2009 17:07:18 -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 20800 invoked by uid 99); 20 Sep 2009 17:07:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Sep 2009 17:07:18 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=FS_REPLICA,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates 72.14.220.157 as permitted sender) Received: from [72.14.220.157] (HELO fg-out-1718.google.com) (72.14.220.157) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Sep 2009 17:07:09 +0000 Received: by fg-out-1718.google.com with SMTP id d23so650317fga.5 for ; Sun, 20 Sep 2009 10:06:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=CFlQJKxVbollpcRzLluiKKhUECOivdNwduCZ5JE7p8U=; b=CpUWHrDPr2BSaXYLcpsdF8yE0UF6P1tMoMjZlKMNISxSy3zGPKi/C5gNaKqoVoxOeG fVEP6VNT8Dzy65ONmtVVCROolMf4E/B3xB4VF47WJhUzabxHSfwjEi3TEz0+FiY2dFcv K/H9NIlCp3lYnPiWKCt1iggwb5c6Uk4x2Tir8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=xqmuMFc1X98g6HwmZ2/fKgeufJNiT7uw3oNBbrC9nelO4qu6xBc3UgaCVchdkJrvNx iZHD+DLtltU599KrZtAIydB17PNPpHSLypzPrFZ2c8HNNggv6g7NTwgzTyKUX/VyqH1i K6NB007FQhMvxEnW7QLwmJCiqQ8CO9/dupYTk= MIME-Version: 1.0 Received: by 10.86.16.9 with SMTP id 9mr3794521fgp.8.1253466409345; Sun, 20 Sep 2009 10:06:49 -0700 (PDT) Date: Sun, 20 Sep 2009 19:06:49 +0200 Message-ID: Subject: continuous replication questions From: Benoit Chesneau To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 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=EEt