[
https://issues.apache.org/jira/browse/OAK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968632#comment-14968632
]
Dheeraj Khanna edited comment on OAK-3054 at 10/22/15 6:31 AM:
---------------------------------------------------------------
Hi [~edivad]
This is a regular ask by customers. Requesting you to kindly bump the priority
on this.
cc [~chetanm], [~alexparvulescu]
Thanks,
was (Author: dheerajkhanna):
Hi [~edivad]
This is a regular ask by customers. There has been recent P1 because of
indexing fails and customers are asking for this feature to take corrective
actions. Requesting you to kindly bump the priority on this.
cc [~chetanm], [~alexparvulescu]
Thanks,
> 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
> Labels: resilience, tooling
> Fix For: 1.3.9, 1.2.8
>
>
> 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)
