[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Story of BerkeleyDB failing

From: Rafael Garcia-Suarez <rgarciasuarez_at_free.fr>
Date: 2002-12-08 21:17:32 CET

Andreas J. Koenig wrote:
> >>>>> On Sun, 08 Dec 2002 15:42:28 +0100, andreas.koenig@anima.de (Andreas J. Koenig) said:
>
> >>>>> On Sun, 8 Dec 2002 15:34:48 +0100, "Sander Striker" <striker@apache.org> said:
> >> Try doubling the values of the following options in DB_CONFIG
>
> >> set_lk_max_locks
> >> set_lk_max_lockers
> >> set_lk_max_objects
>
> > Doubling from 2000 to 4000 each. Same result. I had forgotten to
> > report that I tried that already.
>
> Uh-oh-wait a second: If I now run an 'svnadmin recover' then it works
> indeed.
>
> THANK YOU!

Anyway, is this a scalability problem ? I mean, will those thresholds
need to be increased when the repository this rev #20000 ? Why is this
necessary ? (will undeltifying the repository help here ?)

(And this ought to be mentioned in The Book, for those who don't know
how to administrate a huge Berkeley DB.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 8 21:15:51 2002

This is an archived mail posted to the Subversion Dev mailing list.