jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Eissing (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-5238) IndexCopier causes concurrent update on NodeBuilder
Date Thu, 08 Dec 2016 13:14:59 GMT

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

Stefan Eissing commented on OAK-5238:
-------------------------------------

And if one created/initialized and commited a subnode, took a node builder on that for the
COWDirectory for async copying. On Directory close merged as final task that node and then
moved all contained nodes upward? There can only ever by a single COWDirectory per index at
a time, right? So, gc inside the node store would not be necessary.

> IndexCopier causes concurrent update on NodeBuilder
> ---------------------------------------------------
>
>                 Key: OAK-5238
>                 URL: https://issues.apache.org/jira/browse/OAK-5238
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>    Affects Versions: 1.2.3, 1.0.15, 1.4.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>              Labels: candidate_oak_1_4
>             Fix For: 1.6
>
>         Attachments: OAK-5238.patch
>
>
> OAK-2247 introduced the copy-on-write feature for lucene index in Oak. This feature may
result in a NodeBuilder updated by multiple threads concurrently. New index files are first
stored on the local filesystem and then copied asynchronously into the repository. At the
same time the async index update thread manipulates the node builders as well.
> With MongoMK this results in unexpected conflicts and failed async index updates.



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

Mime
View raw message