[
https://issues.apache.org/jira/browse/SLING-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved SLING-6489.
--------------------------------
Resolution: Won't Fix
I'm hesitant to implement this as it might hide useful information in an error
case. Hence closing as wont fix for now.
> discovery.oak: log less frequent when slingId is not (yet) mapped
> -----------------------------------------------------------------
>
> Key: SLING-6489
> URL: https://issues.apache.org/jira/browse/SLING-6489
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Discovery Oak 1.2.16
> Reporter: Stefan Egli
> Fix For: Discovery Oak 1.2.18
>
>
> When connecting an oak-run in read-write mode to a documentMk based cluster,
> discovery.oak complains with the following info messages repeatedly:
> {noformat}
> 2017-01-27 17:32:09,970 INFO NA
> [discovery.connectors.common.runner.cf92d88d-345a-4e65-b776-f18dde62e585.discoveryLiteCheck]
> o.a.s.d.b.c.BaseDiscoveryService - getTopology: undefined cluster view:
> NO_ESTABLISHED_VIEW]
> org.apache.sling.discovery.base.commons.UndefinedClusterViewException: no
> slingId mapped for clusterNodeId=2
> 2017-01-27 17:32:11,971 INFO NA
> [discovery.connectors.common.runner.cf92d88d-345a-4e65-b776-f18dde62e585.discoveryLiteCheck]
> o.a.s.d.o.c.OakClusterViewService - getLocalClusterView: undefined
> clusterView: NO_ESTABLISHED_VIEW - no slingId mapped for clusterNodeId=2
> 2017-01-27 17:32:11,971 INFO NA
> [discovery.connectors.common.runner.cf92d88d-345a-4e65-b776-f18dde62e585.discoveryLiteCheck]
> o.a.s.d.b.c.BaseDiscoveryService - getTopology: undefined cluster view:
> NO_ESTABLISHED_VIEW]
> org.apache.sling.discovery.base.commons.UndefinedClusterViewException: no
> slingId mapped for clusterNodeId=2
> 2017-01-27 17:32:13,972 INFO NA
> [discovery.connectors.common.runner.cf92d88d-345a-4e65-b776-f18dde62e585.discoveryLiteCheck]
> o.a.s.d.o.c.OakClusterViewService - getLocalClusterView: undefined
> clusterView: NO_ESTABLISHED_VIEW - no slingId mapped for clusterNodeId=2
> 2017-01-27 17:32:13,972 INFO NA
> [discovery.connectors.common.runner.cf92d88d-345a-4e65-b776-f18dde62e585.discoveryLiteCheck]
> o.a.s.d.b.c.BaseDiscoveryService - getTopology: undefined cluster view:
> NO_ESTABLISHED_VIEW]
> org.apache.sling.discovery.base.commons.UndefinedClusterViewException: no
> slingId mapped for clusterNodeId=2
> 2017-01-27 17:32:15,973 INFO NA
> [discovery.connectors.common.runner.cf92d88d-345a-4e65-b776-f18dde62e585.discoveryLiteCheck]
> o.a.s.d.o.c.OakClusterViewService - getLocalClusterView: undefined
> clusterView: NO_ESTABLISHED_VIEW - no slingId mapped for clusterNodeId=2
> {noformat}
> while this is 'by design' (being that oak-run represents only half of the
> expected discovery.oak/discovery-lite stack) we could lower the frequency of
> these messages to keep the log file cleaner. Perhaps log only every 5-10min.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
