jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3069) Provide option to eagerly copy the new index files in CopyOnRead
Date Fri, 03 Jul 2015 10:30:04 GMT

    [ https://issues.apache.org/jira/browse/OAK-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613111#comment-14613111
] 

Chetan Mehrotra commented on OAK-3069:
--------------------------------------

Ideally this should be seen only for first time at time of start. As index is only reopened
if something is written to it. Another case it can happen is when CopyOnWrite is enabled

> Provide option to eagerly copy the new index files in CopyOnRead
> ----------------------------------------------------------------
>
>                 Key: OAK-3069
>                 URL: https://issues.apache.org/jira/browse/OAK-3069
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.2.3, 1.3.3, 1.0.17
>
>         Attachments: OAK-3069+logs-v2.patch, OAK-3069+logs.patch, OAK-3069.patch
>
>
> Currently the CopyOnRead feature lazily starts copying the index files upon first access.
This at times does not work efficiently because the index gets updated frequently and hence
by the time copy is done index would have moved on. Due to this most of the index read turn
out to be remote reads and cause slowness
> We should provide an option on per index basis to enable copying the files eagerly before
exposing the new index to the query engine such that any read done is done locally



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

Mime
View raw message