[
https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807892#comment-16807892
]
Nitin Gupta commented on OAK-8177:
----------------------------------
[~tmueller] - sorry for the to and fro on a trivial change . I have updated the
patch here - [^OAK-8177_3.patch] . Removed the comment , logging stack trace
from second occurrence and changed log.info("Getting checkpoint info for {}",
cp); to log.debug - I think it's best for now - in case we do come across
something suspicious we can always turn on the debug logging manually .
> 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
> Priority: Major
> 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)
