(Short pause for something unprintable to pass down the socket...)
The only explanation I can think of is that we had a latent deadlock in
the code already, and the checkpoining (which is, for all intent and
purposes, a serialization point for the stress.pl threads) was only
hiding it. What we're /probably/ doing is not accessing the tables in
the same order in different code paths, which is an almost certain
recipe for deadlocks.
It's probably just another manifestation of our totally uncontrolled use
of (too large) transactions. If "just another" is the right word. Looks
like I'll have to dig into that mess sooner than I expected, ouch.
Karl Fogel wrote:
>Okay, I'm getting the error too, in three of my five stress.pl
>instances. Here's one example:
>
> Committing:
> Sending wcstress.4553/trunk/bar1/foo1
> Sending wcstress.4553/trunk/bar2/foo1
> Sending wcstress.4553/trunk/bar2/foo2
> Sending wcstress.4553/trunk/foo2
> Transmitting file data .subversion/libsvn_client/commit.c:670: \
> (apr_err=160020)
> svn: Item already exists in filesystem
> svn: Commit failed (details follow):
> subversion/libsvn_fs/bdb/nodes-table.c:146: (apr_err=160020)
> svn: successor id `0.0.u9' (for `0.0.tu') already exists \
> in filesystem '/home/kfogel/src/stress/repostress/db'
> subversion/libsvn_fs/bdb/bdb-err.c:61: (apr_err=160030)
> svn: Berkeley DB deadlock error
> svn: Berkeley DB error while reading node revision for \
> filesystem /home/kfogel/src/stress/repostress/db:
> DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock
> unexpected commit fail: exit status: 256
>
>They all look pretty similar to this. And I just looked at the output
>from my old stress tests, when I had (essentially) revision 5194 as a
>local mod, and it's the same error there too.
>
>I'll try again with revision 5194 subtracted; will post results.
>
>-Karl
>
>
>Philip Martin <philip@codematters.co.uk> writes:
>
>
>>I just tried five instances of stress.pl (r5195) over ra_local and I
>>got a commit error that I have never seen before
>>
>>Updated to revision 193.
>>Committing:
>>Sending wcstress.5717/trunk/bar1/foo1
>>Sending wcstress.5717/trunk/bar2/foo2
>>Sending wcstress.5717/trunk/foo1
>>Sending wcstress.5717/trunk/foo2
>>Transmitting file data ...../svn/subversion/libsvn_client/commit.c:670: (apr_err=160020)
>>svn: Item already exists in filesystem
>>svn: Commit failed (details follow):
>>../svn/subversion/libsvn_fs/bdb/nodes-table.c:146: (apr_err=160020)
>>svn: successor id `2.0.166' (for `2.0.15r') already exists in filesystem '/home/pm/sw/subversion/obj/subversion/tests/repostress/db'
>>../svn/subversion/libsvn_fs/bdb/bdb-err.c:61: (apr_err=160030)
>>svn: Berkeley DB deadlock error
>>svn: Berkeley DB error while reading node revision for filesystem /home/pm/sw/subversion/obj/subversion/tests/repostress/db:
>>DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock
>>unexpected commit fail: exit status: 256
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
>
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 4 20:56:43 2003