[OAK-4836] Avoid excessive logging in case of corrupt index or mis-configured index defnition

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.14, 1.6.0
• Component/s: lucene
• Epic Link: indexer resilience 1.6
• Assignee: Chetan Mehrotra
• Reporter: Vikas Saurabh
• Created: 21/Sep/16 14:54
• Updated: 06/Dec/16 10:36
• Resolved: 20/Nov/16 16:40

Description

Following up from comment[0] from chetanm in OAK-4805, in case of corrupt index or mis-configured index defnition the logs tend to fill up with same exception over and over. It would be useful for index tracker to keep track of such index and ignore those for any processing until some change is detected on the definition (reindex would also lead to a change on index).

We might also want to expose a jmx which lists the indices that tracker thinks are bad (and probably also why it started to think that).

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

Issue Links

• is related to: OAK-4805 Misconfigured lucene index definition can render the whole system unusable
• is related to: OAK-4939 Isolate corrupted index and make async indexer more resilient