You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2016/01/26 13:31:39 UTC

[jira] [Commented] (OAK-3924) Fix database-level row deadlock during bulk updates in RDB

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

Tomek Rękawek commented on OAK-3924:
------------------------------------

Added a proposal solution, which acquires a striped locks before performing batch operations in the {{RDBDocumentStoreJDBC}}. [~reschke], could you take a look on this?

> 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
>             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 presenting the issue.



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