[jira] [Commented] (OAK-4939) Isolate corrupted index and make async indexer more resilient

["Alexander Klimetschek (JIRA)" <ji...@apache.org>]

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

Alexander Klimetschek commented on OAK-4939:
--------------------------------------------

I add an enhancement request in OAK-5519 to be more specific and skip individual binaries/blobs that are creating issues for the indexing (blob can't be found, text extraction throws error etc.), so that the index isn't completely isolated. If the problem is a binary, then it should be isolated there, and wouldn't mean the index itself is corrupted. Of course, it makes sense to track these binaries and see if they can be indexed later when the underlying issue might have been resolved (e.g. manually through by an admin).

> Isolate corrupted index and make async indexer more resilient
> -------------------------------------------------------------
>
>                 Key: OAK-4939
>                 URL: https://issues.apache.org/jira/browse/OAK-4939
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene, query
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.5.15, 1.6
>
>         Attachments: corrupt-index-mbean.png, OAK-4939-v1.diff, OAK-4939-v2.diff
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)