[jira] [Resolved] (OAK-3053) Locking issues seen with CopyOnWrite mode enabled

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra resolved OAK-3053.
----------------------------------
    Resolution: Fixed

Fixed by using NolockFactory to avoid Lucene managing locks! Oak by design ensures such concurrent indexing would not happen
* trunk -  1688421,1688436
* 1.0 - 1688438
* 1.2 - 1688440

> Locking issues seen with CopyOnWrite mode enabled
> -------------------------------------------------
>
>                 Key: OAK-3053
>                 URL: https://issues.apache.org/jira/browse/OAK-3053
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.2.3, 1.3.2, 1.0.17
>
>
> When CopyOnWrite mode is enabled and incremental mode is enabled i.e. {{indexPath}} property set then failure in any indexing cycle would prevent further indexing from progressing. For e.g. if any indexing cycle fails then subsequent indexing cycle would fail with Lucene locking related exception
> {noformat}
> Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@/tmp/junit8067118705344013640/2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae/1/write.lock
> 	at org.apache.lucene.store.Lock.obtain(Lock.java:89)
> 	at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:707)
> 	at org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext.getWriter(LuceneIndexEditorContext.java:169)
> 	at org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditor.addOrUpdate(LuceneIndexEditor.java:293)
> 	... 37 more
> {noformat}
> Any further indexing would continue to fail with this exception



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