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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2015/12/18 16:47:47 UTC

[jira] [Commented] (OAK-3810) Log messages related to AsyncIndexUpdate leaseTimeOut impact

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

Alex Parvulescu commented on OAK-3810:
--------------------------------------

this used to be logged as {{debug}} level [0], but now after OAK-3436, the timeout is considered an indexing error and will be logged (as {{warn}} level) and exposed via JMX too [1].

so simply backporting OAK-3436 will be enough I suppose?



[0] https://github.com/apache/jackrabbit-oak/blob/99d6c8090efd26a259d14462a4da009b3fef70f9/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/AsyncIndexUpdate.java#L276
[1] https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/AsyncIndexUpdate.java#L301


> Log messages related to AsyncIndexUpdate leaseTimeOut impact
> ------------------------------------------------------------
>
>                 Key: OAK-3810
>                 URL: https://issues.apache.org/jira/browse/OAK-3810
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>    Affects Versions: 1.2.9, 1.0.25, 1.3.12
>            Reporter: Thierry Ygé
>
> Currently if the async index is not running it might be due to the leaseTimeOut check. 
> As there are no log messages, it is difficult to analyze why the indexing is not running.
> It would really help to add some log messages about this.



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