Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-2063

Index creation: interruption resilience

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: indexing
    • Labels:

      Description

      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.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              thomasm Thomas Mueller

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment