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 2015/05/22 09:14:17 UTC
[jira] [Resolved] (OAK-2247) CopyOnWriteDirectory implementation
for Lucene for use in indexing
[ https://issues.apache.org/jira/browse/OAK-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra resolved OAK-2247.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.0.15
1.2.3
1.3.0
Committed the patch
* trunk - http://svn.apache.org/r1680903
* 1.0 - http://svn.apache.org/r1680926
* 1.2 - http://svn.apache.org/r1681005
> CopyOnWriteDirectory implementation for Lucene for use in indexing
> ------------------------------------------------------------------
>
> Key: OAK-2247
> URL: https://issues.apache.org/jira/browse/OAK-2247
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Labels: docs-impacting
> Fix For: 1.3.0, 1.2.3, 1.0.15
>
> Attachments: OAK-2247-v1.patch
>
>
> Currently a Lucene index when is written directly to OakDirectory. For reindex case it might happen that Lucene merge policy read the written index files again and then perform a sgement merge. This might have lower performance when OakDirectroy is writing to remote storage.
> Instead of that we can implement a CopyOnWriteDirectory on similar lines to OAK-1724 where CopyOnReadDirectory support copies the index locally for faster access.
> At high level flow would be
> # While writing index the index file is first written to local directory
> # Any write is done locally and once a file is written its written asynchronously to OakDirectory
> # When IndexWriter is closed it would wait untill all the write is completed
> This needs to be benchmarked with existing reindex timings to see it its actually beneficial
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)