db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5448) In the 10.8 branch, back out the concurrency improvements introduced by using SequenceUpdaters to allocate identity values.
Date Sat, 08 Oct 2011 01:29:29 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123343#comment-13123343

Myrna van Lunteren commented on DERBY-5448:

For what it's worth, I kicked off 3 runs yesterday, and so far, there are no deadlocks.

However, on one machine, with sane jars, I did see these errors:
ERROR XSLA6: Cannot recover the database.
ERROR 40XT4: An attempt was made to close a transaction that was still active. The transaction
has been aborted.

The first hint of trouble here was:
org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED  inconsistency in space
management during insert:  slot = 146 getSlotOffset(slot) = 3206 dataWritten = 19 freeSpace
= -15 firstFreeByte = 3149 page = ---------------------------------------------------
page id: Page(378,Container(0, 1153)) Overflow: false PageVersion: 895 SlotsInUse: 159 DeletedRowCount:
93 PageStatus: 1 NextId: 317 firstFreeByte: 3149 freeSpace: -15 totalSpace: 4028 spareSpace:
0% minimumRecordSize : 1 PageSize: 4096

Shall I log a new issue for this, and attach the derby.log?

> In the 10.8 branch, back out the concurrency improvements introduced by using SequenceUpdaters
to allocate identity values.
> ---------------------------------------------------------------------------------------------------------------------------
>                 Key: DERBY-5448
>                 URL: https://issues.apache.org/jira/browse/DERBY-5448
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation, SQL
>    Affects Versions:
>            Reporter: Rick Hillegas
>             Fix For:
>         Attachments: derby-5448-01-aa-backoutConcurrencyChanges.diff, derby-5448-02-aa-backoutDocsChanges.diff
> New errors were seen while running NsTest against the 10.8.2 release candidates. These
errors are recorded as DERBY-5430 and DERBY-5422. The first error is a deadlock which occurs
when inserting into the main table of the test. The second error is a problem clearing the
identity cache. These errors have caused people to lose confidence in the concurrency improvements
introduced by DERBY-4437. We should back the DERBY-4437 changes out of the 10.8 branch and
use the trunk to continue debugging the problems disclosed by NsTest.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message