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 mrtrick@gmail.com designates
 74.125.83.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=AHwtbqUJvOLiaTw/oulcRGXtlxPefQ8bVQBNRf8g4TLZL3NO19XbeOC5QJG1WLaxjU
         u4rMeiSs7qspN9EEnuWycqUNvTRAL4OqtP755RZ56UngYAc3XXxVY8IjvGhDaKU2Y9DV
         R8lGrq7hOwYd68JI5zpYAlSgCKZVMyIx2N8W8=
Message-ID: <4C766ECA.1090100@gmail.com>
Date: Thu, 26 Aug 2010 23:40:26 +1000
From: Patrick Barnes <mrtrick@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Seamless view rebuilding?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I have a database serving documents through a number of intermediary 
application servers, to the users' web browsers.

There are two mechanisms by which documents are modified;
a) Piecemeal updates as a result of user actions. (ie adding or updating 
a record)
b) Bulk updates, typically from import scripts, that might modify tens 
of thousands of documents at once.

The problem I'm having, is that when a set of bulk updates go through, 
it can take a long time to rebuild the view indexes. Meanwhile, several 
user's web requests will time out until rebuilding is complete.

Stale=ok is a simple solution to the bulk problem, but the application 
servers will also expect to be able to update documents, and retrieve 
the changes immediately after.

Is there a good way to avoid these large view update delays?

-Patrick Barnes