You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Brandon Ehle <az...@yahoo.com> on 2002/12/16 17:29:39 UTC
Ran out of DB locks for large commit
On Friday we tried to do a very large commit on a branch of our
repository, svn returned an error saying the the commit succeeded, but
the commit failed. After reverting our repository via svnadmin
load/dump and retrying the commit after adjusting db/DB_CONFIG and uping
all of the lock values from 2000 to 8000, the commit succeeded.
Is there any way to get Berkeley DB to auto-increase the amount of locks
when it runs out?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Ran out of DB locks for large commit
Posted by Brandon Ehle <az...@yahoo.com>.
cmpilato@collab.net wrote:
>Brandon Ehle <az...@yahoo.com> writes:
>
>
>
>>On Friday we tried to do a very large commit on a branch of our
>>repository, svn returned an error saying the the commit succeeded, but
>>the commit failed.
>>
>>
>
>You mean, "commit succeeded, but deltification failed", perhaps?
>
>
>
Yep, thats the one.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Ran out of DB locks for large commit
Posted by cm...@collab.net.
Brandon Ehle <az...@yahoo.com> writes:
> On Friday we tried to do a very large commit on a branch of our
> repository, svn returned an error saying the the commit succeeded, but
> the commit failed.
You mean, "commit succeeded, but deltification failed", perhaps?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org