Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8A09C9D0 for ; Tue, 3 May 2011 10:16:46 +0000 (UTC) Received: (qmail 18822 invoked by uid 500); 3 May 2011 10:16:45 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 18735 invoked by uid 500); 3 May 2011 10:16:44 -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 18727 invoked by uid 99); 3 May 2011 10:16:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 10:16:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bupt.zhlu@gmail.com designates 209.85.213.52 as permitted sender) Received: from [209.85.213.52] (HELO mail-yw0-f52.google.com) (209.85.213.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 10:16:38 +0000 Received: by ywo7 with SMTP id 7so3223922ywo.11 for ; Tue, 03 May 2011 03:16:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=Wgyk85FloLUGKcS1S5GKIc192pEuGqhxysZYR/GEOi4=; b=Xn5rWp9q9AHls12g1b51AW4CVBBuhjZ9glBA7mJiuTet1sRrGXUdSY/1fNKULQCEWK wY/bay90e/GpoXqKR+uHfhck1xXsJcjuyWbJTIs04myroBSJ+QLaG0N3Xbza3VeFE3eo yfBJki+e8QFoRMZVXOTPhlhuLBK0k3JlsfI08= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=sYqvkeRIPjr4VOVl/ic/yQ3I4eq/ksF9rnNxcyqK3vGZGlQsgoiDBQ/fwL1Z21J7Pa fW7Y00Y7Y7G0PNvbDmNcw7TCMAu4x0YzakvuREkSRmSn7nkliVd05Um/oSz7MLQP4LRn OWSxFoiKKfs/F9ChI31oHMUxoyEi87Srjqf3o= MIME-Version: 1.0 Received: by 10.151.47.9 with SMTP id z9mr7406966ybj.306.1304417777812; Tue, 03 May 2011 03:16:17 -0700 (PDT) Received: by 10.151.43.17 with HTTP; Tue, 3 May 2011 03:16:17 -0700 (PDT) Date: Tue, 3 May 2011 18:16:17 +0800 Message-ID: Subject: Is Couchdb a distributed database From: =?GB2312?B?1cXCtw==?= To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=00151750ed344905e604a25c6ed2 --00151750ed344905e604a25c6ed2 Content-Type: text/plain; charset=ISO-8859-1 Hi, As we all know that couchdb can replication each other after we set the replicate rules.Then we can put a balancer such as nginx before Couchdbs(lots of Couchdb which have setted replicate rules). All of the Couchdbs have the same data among them, so the data is redundancy . Is there any way can solve the problem under that scene? --00151750ed344905e604a25c6ed2--