From user-return-7761-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Wed Nov 25 21:49:34 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 47079 invoked from network); 25 Nov 2009 21:49:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Nov 2009 21:49:34 -0000 Received: (qmail 27525 invoked by uid 500); 25 Nov 2009 21:49:32 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 27442 invoked by uid 500); 25 Nov 2009 21:49:32 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 27432 invoked by uid 99); 25 Nov 2009 21:49:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Nov 2009 21:49:32 +0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.68.5.9] (HELO relay00.pair.com) (209.68.5.9) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 25 Nov 2009 21:49:23 +0000 Received: (qmail 26622 invoked from network); 25 Nov 2009 21:49:00 -0000 Received: from 75.143.234.216 (HELO ?192.168.1.33?) (75.143.234.216) by relay00.pair.com with SMTP; 25 Nov 2009 21:49:00 -0000 X-pair-Authenticated: 75.143.234.216 Message-Id: <4BA6AB3F-0EC1-4C1D-9D41-0C2755FB77AA@apache.org> From: Damien Katz To: user@couchdb.apache.org In-Reply-To: <45ae90370911251327y4e8f0553gcd3bda393aa361d9@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: all_dbs_active - what should an app do when it gets this? Date: Wed, 25 Nov 2009 16:49:01 -0500 References: <45ae90370911231435p64486788v6248a03c0d3aac8e@mail.gmail.com> <404484DB-9778-4E45-89AB-7765B640C6A7@apache.org> <45ae90370911231726w6f3fa36ele27fe6b4bbb1b19b@mail.gmail.com> <45ae90370911251002l5d24c346ia61d69c8562c1c6c@mail.gmail.com> <296DB3B0-24B1-487A-8DD7-3ED8FF317C04@apache.org> <1B968FDA-B077-4A53-933F-EF490E5AB0D4@apache.org> <45ae90370911251327y4e8f0553gcd3bda393aa361d9@mail.gmail.com> X-Mailer: Apple Mail (2.936) X-Virus-Checked: Checked by ClamAV on apache.org 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. -Damien 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