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 "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/10/08 14:01:26 UTC

[jira] [Resolved] (OAK-3492) reduce DocumentDiscoveryLiteService hasBacklog WARNs

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

Stefan Egli resolved OAK-3492.
------------------------------
    Resolution: Fixed

added a version-check in revision 1707508.
Note: this must be adjusted when backporting the OAK-2844-feature to the 1.2 branch...
/cc [~catholicon]

> reduce DocumentDiscoveryLiteService hasBacklog WARNs
> ----------------------------------------------------
>
>                 Key: OAK-3492
>                 URL: https://issues.apache.org/jira/browse/OAK-3492
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.3.7
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: 1.3.8
>
>
> With DocumentDiscoveryLiteService in 1.3.7 the following WARN has been noticed:
> {code}
> 07.10.2015 06:38:16.575 *TRACE* [DocumentDiscoveryLiteService-BackgroundWorker-[4]] org.apache.jackrabbit.oak.plugins.document.DocumentDiscoveryLiteService hasBacklog: start. clusterNodeId: 1
> 07.10.2015 06:38:16.575 *TRACE* [DocumentDiscoveryLiteService-BackgroundWorker-[4]] org.apache.jackrabbit.oak.plugins.document.DocumentDiscoveryLiteService getLastKnownRevision: end. clusterNode:
>  1, lastKnownRevision: r14e0c0898cc-0-1
> 07.10.2015 06:38:16.575 *WARN* [DocumentDiscoveryLiteService-BackgroundWorker-[4]] org.apache.jackrabbit.oak.plugins.document.DocumentDiscoveryLiteService hasBacklog: node has lastWrittenRootRev=
> null
> {code}
> This happens every 5sec. While the warning is somewhat legitimate as it cannot determine the backlog of a not-active instance - it is spam if it occurs every 5sec. So rather than warning constantly, there should only be one warning and then a fall-back to log.debug afterwards.



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