[
https://issues.apache.org/jira/browse/OAK-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122206#comment-15122206
]
Marcel Reutegger commented on OAK-3924:
---------------------------------------
FWIW, I'd be in favour of this simplification. AFAIK we don't have client code
that needs this feature.
> 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-01-disable-property.patch,
> OAK-3924-02-concurrent-tests.patch, OAK-3924-03-autocommit.patch,
> OAK-3924-04-sort-documents.patch,
> OAK-3924-05-handle-batch-update-exception.patch, 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)
