Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of ramkrishna.kulkarni@gmail.com
 designates 209.85.218.52 as permitted sender)
MIME-Version: 1.0
Date: Fri, 22 Jul 2011 17:09:13 +0530
Message-ID: 
 <CAKGW8Li=GFoyJd_-=HAmYAgX1pw3uCfr7-tEZ2EyX59EcUxzcA@mail.gmail.com>
Subject: CouchDB filters: {"error":"changes_reader_died"}
From: Ramkrishna Kulkarni <ramkrishna.kulkarni@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=000e0cd56b442d99f104a8a6ea81

--000e0cd56b442d99f104a8a6ea81
Content-Type: text/plain; charset=ISO-8859-1

I have a DB with some 40K documents. I initiate around 40 replications at
the same time with a filter. The filter is a simple string comparison on one
of the fields. On an average, each replication copies 1K documents to the
target DBs. This process takes several minutes (30 minutes sometimes). I
have observed that around 90% of the time is spent in filtering the
documents at source DB (I'm guessing this because CPU is fully loaded at
source for most of the time and once the copying starts, it finishes pretty
quickly). Situation is a little better if the number of simultaneously
replications is less.

This DB has 4 views (composite keys). Tried on 1.0.2 and 1.1.0. Server is a
2 core box running Ubuntu 10.10.
I've seen message like "changes_timeout" and {"error":"changes_reader_**
died"}

Please let me know if there are things to keep in mind while using filters.

Thanks,
Ram

--000e0cd56b442d99f104a8a6ea81--