[
https://issues.apache.org/jira/browse/OAK-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027587#comment-14027587
]
Shashank Gupta commented on OAK-1775:
-------------------------------------
Hi, can it be backported 1.0. it is vital performance fix for our usecase.
thnx.
> 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.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)
