couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damien Katz <>
Subject Re: all_dbs_active - what should an app do when it gets this?
Date Wed, 25 Nov 2009 21:49:01 GMT
I looked again at your crash stack traces. It's caused by a timeout  
while creating the database. It looks like you are very IO bound, and  
creating the databases, which is just creating a new file a writing an  
initial header (< 4k), is timing out. We should probably add an  
infinite timeout there to prevent this crash.


On Nov 25, 2009, at 4:27 PM, Jeff Macdonald wrote:

> On Wed, Nov 25, 2009 at 3:08 PM, Damien Katz <>  
> wrote:
>> I think I know what's happening. With delayed commits each database  
>> waits ~1
>> sec before fully committing to disk. So each database is considered  
>> "open"
>> until that commit happens. So this looks like normal behavior to me.
> Yes, I saw the delayed commits, but I would think the test run of a
> sleep of 1 sec between database creations would allow couchdb to do
> commits and therefore no longer be active. In other words, the first
> database should well be inactive after getting to the creation of the
> 99th database as 99 seconds would of passed.
> I should of said I'm using the standard default.ini.
> -- 
> Jeff Macdonald
> Ayer, MA

View raw message