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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/08/18 08:59:02 UTC

[jira] [Commented] (OAK-5238) IndexCopier causes concurrent update on NodeBuilder

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

Chetan Mehrotra commented on OAK-5238:
--------------------------------------

backported the tests to 1.4 branch with 1805392. It also creates a scenario where index commit goes through but index file nodes created are not proper i.e. they do not have "uniqueKey" property

{noformat}
java.lang.AssertionError: { jcr:lastModified = 1503046242302, jcr:data = [1026 binaries] }
	at org.junit.Assert.fail(Assert.java:88)
	at org.apache.jackrabbit.oak.plugins.index.lucene.CopyOnWriteDirectory_Segment_Test.assertIndexState(CopyOnWriteDirectoryTest2.java:151)
	at org.apache.jackrabbit.oak.plugins.index.lucene.CopyOnWriteDirectory_Segment_Test.copyOnWrite_largeFile(CopyOnWriteDirectoryTest2.java:144)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
{noformat}

> 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_4
>             Fix For: 1.5.16, 1.6.0
>
>         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)