sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothee Maret (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-8620) Journal Distribution discovery service should log topology changes at INFO level
Date Thu, 08 Aug 2019 08:01:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-8620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902772#comment-16902772
] 

Timothee Maret commented on SLING-8620:
---------------------------------------

Opened [PR|https://github.com/apache/sling-org-apache-sling-distribution-journal/pull/10]

> 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
>          Time Spent: 10m
>  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)

Mime
View raw message