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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2018/03/08 14:51:00 UTC

[jira] [Resolved] (OAK-2063) Index creation: interruption resilience

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

Thomas Mueller resolved OAK-2063.
---------------------------------
    Resolution: Won't Fix

With oak-run indexing, I think this is no longer needed. 

> Index creation: interruption resilience
> ---------------------------------------
>
>                 Key: OAK-2063
>                 URL: https://issues.apache.org/jira/browse/OAK-2063
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: indexing
>            Reporter: Thomas Mueller
>            Priority: Major
>              Labels: resilience
>
> Creating an index can take a long time. If it is interrupted (for example because the process was stopped or died), then it would be nice if after a restart reindexing would continue where it was stopped. I'm not sure how complicated this is.
> There are some more potential problems that should be documented / tested: 
> * When creating a new index in a cluster, which instance creates the index?
> * When creating multiple indexes at the same time, is the repository only scanned once (and not once per index)? 
> * The same when manually triggering a reindex using the "reindex" flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)