[
https://issues.apache.org/jira/browse/SLING-11026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050584#comment-18050584
]
Timothee Maret commented on SLING-11026:
----------------------------------------
Thanks for filing this ticket !
Do I understand it correctly that the intention is to change the pool from
```
content-distribution
```
to
```
org-apache-sling-distribution
```
?
While I think the change is rather harmless, I wonder if there's anything
behind this change more than aligning pool names.
> Distribution should use its own threadpool of scheduled events
> --------------------------------------------------------------
>
> Key: SLING-11026
> URL: https://issues.apache.org/jira/browse/SLING-11026
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
> Affects Versions: Content Distribution Core 0.4.6, Content Distribution
> Journal Messages 0.3.0
> Reporter: Joerg Hoh
> Assignee: Timothee Maret
> Priority: Major
> Labels: good-first-issue
>
> Sling distribution should use its own threadpool for scheduled events instead
> of the default threadpool.
> affected classes:
> * org.apache.sling.distribution.journal.impl.precondition.StagingPrecondition
> * org.apache.sling.distribution.journal.queue.impl.PubQueueProviderImpl
> * org.apache.sling.distribution.journal.impl.discovery.DiscoveryService
> *
> org.apache.sling.distribution.packaging.impl.ResourceDistributionPackageCleanup
> These scheduled jobs should use a dedicated thread-pool
> "org-apache-sling-distribution", for details see the
> [documentation|https://sling.apache.org/documentation/bundles/scheduler-service-commons-scheduler.html#using-dedicated-thread-pools-1]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
