[
https://issues.apache.org/jira/browse/OAK-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689083#comment-15689083
]
Chetan Mehrotra commented on OAK-4939:
--------------------------------------
I remember that. However at that time we were logging exception stack also
which caused more churn. I have now updated the logic to log such a warning
with min delay of 15 mins (default)
{noformat}
2016-11-23 11:26:07,842 WARN NA [async-index-update-fulltext-async]
o.a.j.o.p.i.TrackingCorruptIndexHandler - Ignoring corrupt index
[/oak:index/lucene] which has been marked as corrupt [since Wed Nov 23 11:22:58
IST 2016 ,3 indexing cycles, failed 9 times, skipped 3 time]. This index MUST
be reindexed for indexing to work properly
{noformat}
> 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)
