[jira] [Commented] (SLING-11026) Distribution should use its own threadpool of scheduled events

["Bhavik Kothari (Jira)" <ji...@apache.org>]

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

Bhavik Kothari commented on SLING-11026:
----------------------------------------

Raised a new PR for the core bundle as suggested:
https://github.com/apache/sling-org-apache-sling-distribution-core/pull/75

This replaces #73 and includes the change for VaultDistributionPackageBuilderFactory 
to use the dedicated thread pool `org-apache-sling-distribution`.

> 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
>            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)