[OAK-4939] Isolate corrupted index and make async indexer more resilient

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.15, 1.6.0
• Component/s: lucene, query
• Labels: docs-impacting
• Epic Link: indexer resilience 1.6
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 17/Oct/16 04:31
• Updated: 08/Oct/19 15:22
• Resolved: 23/Nov/16 06:21

Description

Currently if any one of the async index gets corrupted it brings down the whole async indexer and no other index gets updated untill system administrator reindexes the problamatic async index.

Instead of fail all we should isolate such corrupted index and mark them as corrupted. And still let async indexer progress for other working indexes.

This would ensure that one corrupted index does not affect the whole system and allow the application to work partially.

Feature branch - https://github.com/chetanmeh/jackrabbit-oak/compare/trunk...chetanmeh:OAK-4939?expand=1

Issue Links

• is related to: OAK-5519 Skip problematic binaries instead of blocking indexing
• relates to: OAK-4836 Avoid excessive logging in case of corrupt index or mis-configured index defnition
• supercedes: OAK-3813 Exception in datastore leads to async index stop indexing new content