Thomas Mueller commented on OAK-4939:

This sounds good to me. I would use "corrupt" and not "corrupted". Instead of a 
boolean property, I would use the date and time it got corrupt, so that it's 
easier to analyze (look at the right error.log file).

> 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
> 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. 

This message was sent by Atlassian JIRA

Reply via email to