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 139CC1A2E for ; Fri, 22 Apr 2011 19:37:24 +0000 (UTC) Received: (qmail 5074 invoked by uid 500); 22 Apr 2011 19:37:22 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 5035 invoked by uid 500); 22 Apr 2011 19:37:22 -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 5026 invoked by uid 99); 22 Apr 2011 19:37:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Apr 2011 19:37:22 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.212.52] (HELO mail-vw0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Apr 2011 19:37:16 +0000 Received: by vws16 with SMTP id 16so1043042vws.11 for ; Fri, 22 Apr 2011 12:36:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.97.229 with SMTP id ed5mr2120547vdb.237.1303501014879; Fri, 22 Apr 2011 12:36:54 -0700 (PDT) Received: by 10.220.100.13 with HTTP; Fri, 22 Apr 2011 12:36:54 -0700 (PDT) In-Reply-To: <527BE431-0D7E-4F6C-8E7F-C3490C28B66A@sri.com> References: <527BE431-0D7E-4F6C-8E7F-C3490C28B66A@sri.com> Date: Fri, 22 Apr 2011 21:36:54 +0200 Message-ID: Subject: Re: Scaling CouchDB From: Jonathan Weiss To: user@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org > 2. Is there a strategy to for disk spanning to go beyond the 1TB limit by= incorporating multiple volumes or do we need to leverage a solution like B= igCouch which seems to require us to spin up multiple CouchDB's and do some= sort of sharding/partitioning of data? =C2=A0I'm curious on how queries th= at span shards/partitions works or if this is transparent. We (Scalarium - an EC2 cluster management solution BTW :-) run many servers with > 1TB disks thanks to software RAID over multiple EBS volumes. It not only help avoid the 1TB limitation but also improves performance and reliability. Jonathan --=20 Jonathan Weiss http://blog.innerewut.de http://twitter.com/jweiss