couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Anderson" <jch...@gmail.com>
Subject Re: Couch processes...
Date Fri, 09 Jan 2009 23:05:51 GMT
Does the test suite pass for you?

Thanks,
Chris

On Fri, Jan 9, 2009 at 2:05 PM, Chris Van Pelt <vanpelt@gmail.com> wrote:
> I know, I dumped and loaded.  I can access individual documents fine.
> It's the view generation that is borked.
>
> Chris
>
> On Fri, Jan 9, 2009 at 1:58 PM, Chris Anderson <jchris@gmail.com> wrote:
>> Upgrading existing databases from 0.8.1 requires a dump/load cycle as
>> the backing file format store has changed. See
>> http://wiki.apache.org/couchdb/Breaking_changes for help.
>>
>> On Fri, Jan 9, 2009 at 1:29 PM, Chris Van Pelt <vanpelt@gmail.com> wrote:
>>> I recently upgraded to trunk and now my DB is misbehaving.  It's
>>> having trouble generating my view.  I'm wondering if there is a good
>>> way to figure out where Couch is spending all of it's time.
>>>
>>> Upon requesting the view, I see a couchjs process fired off, and than
>>> my beam.smp process starts to pick up steam.  The beam.smp process
>>> sits around 100% CPU and slowly grows in memory consumption.  couchjs
>>> process chills at around 8% CPU, often times another couchjs process
>>> is fired off as well.  Both of these processes tend to slowly decrease
>>> in resource consumption.  I looked in my .dbname view directory and
>>> noticed that the view file grows in size initially to about 14MB, then
>>> beam.smp sits at 100% CPU for 15-20 minutes before the view files
>>> changes in size.
>>>
>>> Since updating to trunk the view seems to never finish rendering.  I
>>> have 9000 documents and 8.1 was rendering it slowly, but it was able
>>> to render it.  I just rewrote my mapReduce to look more like a
>>> mapCombine and tried to regenerate the view.  It's been 30 minutes,
>>> the view file is still at 14MB, nothing has been written to the log, I
>>> have 2 couchjs process at about 5% CPU and the beam.smp process is at
>>> 85%.
>>>
>>> Is there a good way to debug this?  One other interesting thing I
>>> noticed was the couchdb executable actually launching two identical
>>> processes...
>>>
>>> Any help would be much appreciated.
>>>
>>> Chris
>>>
>>
>>
>>
>> --
>> Chris Anderson
>> http://jchris.mfdz.com
>>
>



-- 
Chris Anderson
http://jchris.mfdz.com

Mime
View raw message