jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3924) Fix database-level row deadlock during bulk updates in RDB
Date Thu, 28 Jan 2016 13:21:39 GMT

    [ https://issues.apache.org/jira/browse/OAK-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15121405#comment-15121405
] 

Julian Reschke commented on OAK-3924:
-------------------------------------

With the patch, {ConcurrentDocumentStoreTest.testConcurrenCreateOrUpdate()} fails for me (createOrUpdate
always returns null).

(and yes, there's a typo in the test name)

> Fix database-level row deadlock during bulk updates in RDB
> ----------------------------------------------------------
>
>                 Key: OAK-3924
>                 URL: https://issues.apache.org/jira/browse/OAK-3924
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: rdbmk
>            Reporter: Tomek Rękawek
>            Priority: Critical
>             Fix For: 1.4
>
>         Attachments: OAK-3924.patch
>
>
> It seems that the new bulk createOrUpdate() implementation in RDB is prone for the deadlocks.
It isn't a bug in the Oak code, but rather something related to the database implementations.
The bug can be observed if we have multiple  simultaneous bulk updates and some of the rows
repeat among them. The attached patch contains an unit test {{testConcurrentWithConflict}}
presenting the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message