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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2019/04/03 14:11:00 UTC

[jira] [Resolved] (OAK-8177) Add logging around getReferenceCheckpoint method

     [ https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Mueller resolved OAK-8177.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.12.0

> Add logging around getReferenceCheckpoint method 
> -------------------------------------------------
>
>                 Key: OAK-8177
>                 URL: https://issues.apache.org/jira/browse/OAK-8177
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: composite, lucene
>            Reporter: Nitin Gupta
>            Assignee: Thomas Mueller
>            Priority: Major
>             Fix For: 1.12.0
>
>         Attachments: OAK-8177_1.patch, OAK-8177_2.patch, OAK-8177_3.patch
>
>
> 04.03.2019 06:42:46.956 *WARN* [sling-oak-3-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] org.apache.jackrabbit.oak.composite.CompositeNodeStore Checkpoint f7e6524d-62c4-4589-8137-ca873cec934b doesn't exist
> The above warning was observed - but there are not enough logs around this to identify what's causing this .
>  
> We need to add stack trace when this is logged and probably changed the message to make it unique.
>  
> Also , Since this was logged from a flow in AsyncIndexUpdate - It would make sense to add some more info/ warn level logging there around the code that calls getReferenceCheckpoint()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)