[
https://issues.apache.org/jira/browse/SLING-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114941#comment-17114941
]
Timothee Maret edited comment on SLING-9465 at 5/23/20, 9:07 PM:
-----------------------------------------------------------------
Pushed the approach with dynamic reference in PR
[#29|https://github.com/apache/sling-org-apache-sling-distribution-journal/pull/29].
It is untested but descriptive enough to show the pattern and how it could be
for other components (like in SLING-9464). The DiscoveryService does not get
reactivated when adding or removing publisher agent configuration unless 0
configuration remains after the operation.
There are some caveat though, editing a single publisher agent configuration
agent config will trigger reactivations. I assume because the editing is
implemented as a remove/add sequence of operations.
was (Author: marett):
Pushed the approach with dynamic reference in PR
[#29|[https://github.com/apache/sling-org-apache-sling-distribution-journal/pull/29]].
It is untested but descriptive enough to show the pattern and how it could be
for other components (like in SLING-9464). The DiscoveryService does not get
reactivated when adding or removing publisher agent configuration unless 0
configuration remains after the operation.
There are some caveat though, editing a single publisher agent configuration
agent config will trigger reactivations. I assume because the editing is
implemented as a remove/add sequence of operations.
> DiscoveryService is activated on all services
> ---------------------------------------------
>
> Key: SLING-9465
> URL: https://issues.apache.org/jira/browse/SLING-9465
> Project: Sling
> Issue Type: Bug
> Components: Content Distribution
> Reporter: Timothee Maret
> Assignee: Timothee Maret
> Priority: Major
> Fix For: Content Distribution Journal Core 0.1.12
>
>
> The DiscoveryService service is only required on services running the
> DistributionPublisher agents. The DiscoveryServices consumes resources
> (connections, data volume) which should be avoided.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
