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

["Alex Parvulescu (JIRA)" <ji...@apache.org>]

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

Alex Parvulescu commented on OAK-2063:
--------------------------------------

bq. When creating multiple indexes at the same time, is the repository only scanned once (and not once per index)?
all of the available indexes are merged into a composite index and there is only a single pass over the content. the async ones will be merged together separately but along the same lines: single pass over the content.

bq. The same when manually triggering a reindex using the "reindex" flag.
same as above


An interesting side-effect of this is that if one index is slow on insert it will effectively slow down the traversal and block the others from finishing.

> Index creation: interruption resilience
> ---------------------------------------
>
>                 Key: OAK-2063
>                 URL: https://issues.apache.org/jira/browse/OAK-2063
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Thomas Mueller
>            Priority: Minor
>              Labels: resilience
>             Fix For: 1.1, 1.0.7
>
>
> 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
(v6.3.4#6332)