[OAK-3492] reduce DocumentDiscoveryLiteService hasBacklog WARNs

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.7
• Fix Version/s: 1.3.8, 1.4
• Component/s: core
• Assignee: Stefan Egli
• Reporter: Stefan Egli
• Created: 07/Oct/15 10:54
• Updated: 26/Sep/19 11:40
• Resolved: 08/Oct/15 12:01

Description

With DocumentDiscoveryLiteService in 1.3.7 the following WARN has been noticed:

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

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.

Issue Links

• causes: OAK-8139 DocumentDiscoveryLiteService hasBacklog silencing must support maven version format
• is related to: OAK-2844 Introducing a simple document-based discovery-light service (to circumvent documentMk's eventual consistency delays)