You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/11/15 18:07:58 UTC
[jira] [Assigned] (OAK-4836) Avoid excessive logging in case of
corrupt index or mis-configured index defnition
[ https://issues.apache.org/jira/browse/OAK-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra reassigned OAK-4836:
------------------------------------
Assignee: Chetan Mehrotra (was: Vikas Saurabh)
> Avoid excessive logging in case of corrupt index or mis-configured index defnition
> ----------------------------------------------------------------------------------
>
> Key: OAK-4836
> URL: https://issues.apache.org/jira/browse/OAK-4836
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.6
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)