Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 65899 invoked from network); 27 Feb 2009 00:07:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Feb 2009 00:07:27 -0000 Received: (qmail 94619 invoked by uid 500); 27 Feb 2009 00:07:20 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 94536 invoked by uid 500); 27 Feb 2009 00:07:20 -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 94514 invoked by uid 99); 27 Feb 2009 00:07:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2009 16:07:20 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates 209.85.200.170 as permitted sender) Received: from [209.85.200.170] (HELO wf-out-1314.google.com) (209.85.200.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2009 00:07:11 +0000 Received: by wf-out-1314.google.com with SMTP id 28so878884wff.29 for ; Thu, 26 Feb 2009 16:06:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=osrEsLuV6E1VwCybwdw6aDjZxlEIpqRTDUAdfCk1Wqw=; b=ePNxuqU3MaDswV0I4LzoePjSJ6TIc9p3GKtrF/RKvUP55oh5rCKIDReEt+gOjreOMR DL0r/TnVNPCxmwT9Vqnc0vhKU6O8E+iiUkv00YeOVotMsl8PsCUceL1X+TEewfhYkrBg rKvFkoJOJWzImnU9waF31+6ubDbCsoOfd5PBE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=yC/2MJ8I4cVmw+aG533DZf/55NXWgwbNqNSNxkuFboLFBXxcR8OQoEhiSv7dSMuE0r UlJnL7ojAb1VrDOpJUawWG+MJ3mU2dspQeynKN51deo/VbIuYU8dfa9U6qu36z+KTxoJ 0HF5OkokRJ24+O4i4xkJGq394h7zwtmTMwAak= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.142.43.7 with SMTP id q7mr925430wfq.155.1235693209774; Thu, 26 Feb 2009 16:06:49 -0800 (PST) In-Reply-To: References: <56a83cd00902260948x15ce887u4916cedd54959c6@mail.gmail.com> <7898CB93-1504-40B6-8EB8-C4C816189EB8@apache.org> <73AF9D27-6895-4E0D-96E0-335C02B94892@gmail.com> Date: Thu, 26 Feb 2009 16:06:49 -0800 X-Google-Sender-Auth: 4fa047f6264c6e1f Message-ID: Subject: Re: CouchDB and clustering From: Chris Anderson To: user@couchdb.apache.org, dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Feb 26, 2009 at 3:56 PM, Ben Browning wrote: > I think I've captured, at least at a high-level, the general consensus > on partitioning here: > > http://wiki.apache.org/couchdb/Partitioning_proposal > This looks great to me, thanks for capturing it here! The actual hashing of docids and merging of view queries will probably not be the hard part. I expect the hard part to be configuration and management of nodes across machines, as well as communication between nodes. There has been some work to make CouchDB more OTP-like (having trouble finding links...) and I think doing that first could make the rest of this job much easier. Thinking we should move this conversation to dev@ to ensure we get the right people's attention. ('scuse the cross-post.) Chris -- Chris Anderson http://jchris.mfdz.com