[
https://issues.apache.org/jira/browse/OAK-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16132081#comment-16132081
]
Chetan Mehrotra edited comment on OAK-5238 at 8/18/17 12:30 PM:
----------------------------------------------------------------
Changes for this specific issue can be backported with slight change avoiding
dependency on fixes for OAK-5175,OAK-5075.
Merged to
* 1.4 - 1805402
* 1.2 - 1805409
was (Author: chetanm):
Changes for this specific issue can be backported with slight change avoiding
dependency on fixes for OAK-5175,OAK-5075.
Merged to
* 1.4 - 1805402
> 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.0.15, 1.2.3, 1.4.0
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Labels: candidate_oak_1_0
> Fix For: 1.5.16, 1.6.0, 1.4.18, 1.2.28
>
> Attachments: OAK-5238-1.patch, OAK-5238-2.patch, 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.4.14#64029)
