jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing
Date Wed, 08 Jul 2015 12:39:04 GMT

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

Davide Giannella commented on OAK-3054:
---------------------------------------

[~alex.parvulescu]

bq. I recently found out about the CheckpointManger mbean (OAK-2267), does that help?

Awesome! Perfect for my purposes :)

> IndexStatsMBean should provide some details if the async indexing is failing
> ----------------------------------------------------------------------------
>
>                 Key: OAK-3054
>                 URL: https://issues.apache.org/jira/browse/OAK-3054
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.2.3, 1.3.3, 1.0.17
>
>
> If the background indexing fails for some reason it logs the exception for the first
time then it logs the exception like _The index update failed ..._. After that if indexing
continues to fail then no further logging is done so as to avoid creating noise.
> This poses a problem on long running system where original exception might not be noticed
and index does not show updated result. For such cases we should expose the indexing health
as part of {{IndexStatsMBean}}. Also we can provide the last recorded exception. 
> Administrator can then check for MBean and enable debug logs for further troubleshooting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message