[OAK-2063] Index creation: interruption resilience

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: indexing
• Labels: resilience
• Epic Link: indexer resilience
• Assignee: Unassigned
• Reporter: Thomas Mueller
• Created: 01/Sep/14 09:10
• Updated: 08/Mar/18 14:50
• Resolved: 08/Mar/18 14:50

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.

Issue Links

• is related to: OAK-1844 Verify resilience goals
• is related to: OAK-5833 Intermediate commits during (re-)indexing of synchronous index
• relates to: OAK-6081 Indexing tooling via oak-run
• relates to: OAK-2556 Intermediate commit during async indexing