[OAK-5519] Skip problematic binaries instead of blocking indexing

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.12, 1.8.0
• Component/s: indexing
• Labels: resilience
• Epic Link: indexer resilience
• Sprint: L15
• Assignee: Thomas Mueller
• Reporter: Alexander Klimetschek
• Created: 25/Jan/17 23:45
• Updated: 08/Oct/19 15:21
• Resolved: 09/Nov/17 17:08

Description

If a text extraction is blocked (weird PDF) or a blob cannot be found in the datastore or any other error upon indexing one item from the repository that is outside the scope of the indexer, it currently halts the indexing (lane). Thus one item (that maybe isn't important to the users at all) can block the indexing of other, new content (that might be important to users), and it always requires manual intervention (which is also not easy and requires oak experts).

Instead, the item could be remembered in a known issue list, proper warnings given, and indexing continue. Maintenance operations should be available to come back to reindex these, or the indexer could automatically retry after some time. This would allow normal user activity to go on without manual intervention, and solving the problem (if it's isolated to some binaries) can be deferred.

I think the line should probably be drawn for binary properties. Not sure if other JCR property types could trigger a similar issue, and if a failure in them might actually warrant a halt, as it could lead to an "incorrect" index, if these properties are important. But maybe the line is simply a try & catch around "full text extraction".

Issue Links

• breaks: OAK-7508 Text extraction timeout can lead to NPE
• relates to: OAK-3813 Exception in datastore leads to async index stop indexing new content
• relates to: OAK-6967 Skip problematic binaries: spurious warning in log file
• relates to: OAK-4939 Isolate corrupted index and make async indexer more resilient