Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <49035C8E.3020401@isshen.com>
Date: Sat, 25 Oct 2008 13:51:10 -0400
From: Ho-Sheng Hsiao <hosh@isshen.com>
Organization: Isshen Solutions, Inc.
User-Agent: Thunderbird 2.0.0.17 (X11/20081020)
MIME-Version: 1.0
To: couchdb-user@incubator.apache.org
Subject: Re: CouchDB data replication question
References: <1224941547.3020.10.camel@localhost>
In-Reply-To: <1224941547.3020.10.camel@localhost>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


Lucas Di Pentima wrote:
> I'm looking for a storage solution for a website that currently generate
> 1 GB worth of MySQL (the current storage method) new data every month.
>
> I know from browsing this mailing list archives that all the data is
> replicated on all the nodes of a CouchDB cluster, and I see this as a
> scalability problem that I would like to know if have some workaround.

I have not tried clustering or replicating couchdb. I thought I saw
something mentioned though, that you could replicate data based on
arbitrary map calls?

At the very least, you should be able to pull a subset of the data and
make a POST to _bulk_docs on a different node.

Ho-Sheng Hsiao, VP of Engineering
Isshen Solutions, Inc.
(334) 559-9153
http://www.isshen.com