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 "Jukka Zitting (JIRA)" <ji...@apache.org> on 2014/06/13 01:31:03 UTC

[jira] [Updated] (OAK-1775) Avoid lock contention in IndexTracker.getIndexNode()

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

Jukka Zitting updated OAK-1775:
-------------------------------

    Fix Version/s: 1.0.1

Merged to the 1.0 branch in revision 1602316.

> Avoid lock contention in IndexTracker.getIndexNode()
> ----------------------------------------------------
>
>                 Key: OAK-1775
>                 URL: https://issues.apache.org/jira/browse/OAK-1775
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: oak-lucene
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 1.0.1, 1.1
>
>
> It turns out that the approach in OAK-1722 of keeping the {{IndexTracker.getIndexNode()}} method synchronized while the more expensive {{update()}} method is unsynchronized suffers from lock contention in cases where lots of queries are executed concurrently. Thus we should go with Chetan's original suggestion of avoiding exclusive synchronization of the {{getIndexNode()}} method.



--
This message was sent by Atlassian JIRA
(v6.2#6252)