[
https://issues.apache.org/jira/browse/OAK-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989655#comment-14989655
]
Chetan Mehrotra commented on OAK-3547:
--------------------------------------
I think this approach should only affect the flow on Query side. If the index
gets corrupted we should let AsyncIndexUpdate fail. The purpose of this feature
is to avoid immediate downtime.
Another option would be to mark that index as kind of disabled so that it does
not block the indexing cycle and set its reindex flag set to true. Then either
it gets automatically reindex in next cycle or we expose some JMX operation so
that admin can determine when the reindexing is performed
> Improve ability of the OakDirectory to recover from unexpected file errors
> --------------------------------------------------------------------------
>
> Key: OAK-3547
> URL: https://issues.apache.org/jira/browse/OAK-3547
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Affects Versions: 1.4
> Reporter: Ian Boston
>
> Currently if the OakDirectory finds that a file is missing or in some way
> damaged, and exception is thrown which impacts all queries using that index,
> at times making the index unavailable. This improvement aims to make the
> OakDirectory recover to a previously ok state by storing which files were
> involved in previous states, and giving the code some way of checking if they
> are valid.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
