[jira] [Resolved] (SLING-8620) Journal Distribution discovery service should log topology changes at INFO level

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (SLING-8620) Journal Distribution discovery service should log topology changes at INFO level

Oliver Lietz (Jira)

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

Timothee Maret resolved SLING-8620.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Content Distribution Journal Core 0.1.6

> Journal Distribution discovery service should log topology changes at INFO level
> --------------------------------------------------------------------------------
>
>                 Key: SLING-8620
>                 URL: https://issues.apache.org/jira/browse/SLING-8620
>             Project: Sling
>          Issue Type: Improvement
>          Components: Content Distribution
>    Affects Versions: Content Distribution Journal Core 0.1.6
>            Reporter: Timothee Maret
>            Assignee: Timothee Maret
>            Priority: Major
>             Fix For: Content Distribution Journal Core 0.1.6
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The distribution journal discovery [service|https://github.com/apache/sling-org-apache-sling-distribution-journal/blob/master/src/main/java/org/apache/sling/distribution/journal/impl/publisher/DiscoveryService.java] computes delta between views and [logs|https://github.com/apache/sling-org-apache-sling-distribution-journal/blob/master/src/main/java/org/apache/sling/distribution/journal/impl/publisher/DiscoveryService.java#L127] the views upon change. Instead of logging at DEBUG level, we should log it at INFO level. This information is useful to understand how subscribers are announced.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)