[
https://issues.apache.org/jira/browse/OAK-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687113#comment-15687113
]
Chetan Mehrotra commented on OAK-4939:
--------------------------------------
Thanks Alex for the review!
bq. A question regarding the warning
Yes it would be logged on every cycle. Note that it would only be a message not
include any exception trace.Reason for keeping this verbose is to ensure that
it gets picked up by system admin as its an error condition requiring admin
intervention.
Updated the branch as per feedback.
> 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.6, 1.5.15
>
> Attachments: OAK-4939-v1.diff, OAK-4939-v2.diff,
> corrupt-index-mbean.png
>
>
> 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)
