Re: <help>Database is Wedged for the 6th time. Diagnostics or Prozac, anyone?

On Mar 4, 2005, at 4:39 PM, Peter Kahn wrote:

> Below was my email from the 5th crash. I'm now up to the 6th. The
> difference this time is that I didn't have websvn running.
>
> I am coming to the conclusion that the svnserve executable is not ready
> for production. Switching my users back from svn to http is going to
> hurt, but at this point I can see no other alternative.
>

I don't see any evidence that this problem is related to svnserve. Why
do you think that?

> Does anyone have any suggestions on what I can do to make my
> environment
> stable?

Your errors are coming from BDB running out of some sort of resources:

> svn: Berkeley DB error while checkpointing after Berkeley DB
> transaction
> for filesystem /home/svn/repos/db:
> DB_INCOMPLETE: Cache flush was unable to complete

I wonder if the db cache is too small. We've changed the default BDB
cache size in svn 1.2. This is from the DB_CONFIG that 'svnadmin
create' now generates:

# The default cache size in BDB is only 256k. As explained in
# http://svn.haxx.se/dev/archive-2004-12/0369.shtml, this is too
# small for most applications. Bump this number if "db_stat -m"
# shows too many cache misses.
set_cachesize 0 1048576 1

So what I would do is:

1. increase the cache size, then run 'svnadmin recover'

2. stop deltifying in the post-commit hook. The deltification happens
anyway. All you're doing is creating extra BDB traffic for no reason.
This may cause you to hit cache limits even faster.

If these things make no difference, then switch to FSFS.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 5 00:04:04 2005