[
https://issues.apache.org/jira/browse/SLING-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17115356#comment-17115356
]
Timothee Maret commented on SLING-9465:
---------------------------------------
[~cschneider] Yes, using a marker service is the idea in all the PRs. The
pattern would be generalisable to other services that need to be activates only
together with DistributionPublisher services (like the queue cache service).
Instead of using the config admin (PR #32) we could indeed think of registering
the marker service upon activation of DistributionPublisher agents. To avoid
leaking marker services and avoid reactivation loops, the marker service would
be registered only once (independently of the number of DistributionPublisher
agents) and would not be removed by DistributionPublisher agents. Unlike with
PR #32, the marker may never be removed until the instance stops. I am not sure
if it's way simpler but I'll give it a try.
> 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)
