On Fri, Aug 17, 2001 at 12:42:30PM -0700, Greg Stein wrote:
> On Fri, Aug 17, 2001 at 05:07:54AM -0500, kfogel@collab.net wrote:
> >...
> > The showstopper appears to be caused by unfreed Berkeley DB resources.
> > We had some scripts do massive numbers of multi-file commits against a
> > repository, and eventually it starts failing, with (among other
> > things) DB_INCOMPLETE errors, in both ra_local and ra_dav case. See
> > http://www.sleepycat.com/docs/api_c/db_close.html for more on that.
>
> The point here is that we were running serial tests against the repository.
> There should have been only one accessor at a time. Yet the db->close docs
> describe DB_INCOMPLETE as occurring when another writer is working during
> the close operation. That would seem to indicate some transaction is still
> open. It is possible that we were closing an operation (i.e. we didn't hook
> it to a pool).
Would one of these help you track this down:
http://www.sleepycat.com/docs/api_c/txn_stat.html
http://www.sleepycat.com/docs/api_c/lock_stat.html
--
albert chin (china@thewrittenword.com)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:36 2006