[
https://issues.apache.org/jira/browse/OAK-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-1722:
---------------------------------
Attachment: OAK-1722-improve-concurrency.patch
IndexTracker currently is heavily synchronized both for read and writes. Given
that Observor would invoke IndexTracker#update for every change in Oak repo
(even though no change in Index) it might block access to IndexNode.
[Attached patch|^OAK-1722-improve-concurrency.patch] aims to free up the read
part from synchronized lock.
[~jukkaz] Can you review the patch
> Use a shared IndexSearcher for performing Lucene queries
> --------------------------------------------------------
>
> Key: OAK-1722
> URL: https://issues.apache.org/jira/browse/OAK-1722
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Chetan Mehrotra
> Assignee: Jukka Zitting
> Fix For: 1.0, 1.1
>
> Attachments: OAK-1722-improve-concurrency.patch
>
>
> Currently the Lucene integrations opens a new IndexSeracher for every read
> call. This proves to be costly as per OAK-1702. Instead we should use a
> shared IndexSearcher based on approach taken in Lucene
> [SearcherManager|https://lucene.apache.org/core/3_6_0/api/all/org/apache/lucene/search/SearcherManager.html].
> Further there needs to be a way to pickup any changes in Lucene index across
> cluster nodes
--
This message was sent by Atlassian JIRA
(v6.2#6252)
