[
https://issues.apache.org/jira/browse/SLING-12349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853054#comment-17853054
]
Carsten Ziegeler commented on SLING-12349:
------------------------------------------
as far as I remember, that configuration was intended to do what you want
> Unable to set a maximum amount of Sling Jobs in parallel
> ---------------------------------------------------------
>
> Key: SLING-12349
> URL: https://issues.apache.org/jira/browse/SLING-12349
> Project: Sling
> Issue Type: Bug
> Components: Event
> Reporter: Roy Teeuwen
> Priority: Major
>
> It is possible to set a maximum parallel of sling jobs on a queue
> configuration, but in systems where the platform itself already makes 20
> queue's and the customer's code also add's their own queue's, this
> configuration makes no sense because it is set per queue and not overall. The
> sum of the parallel could be way more than the amount of cores available,
> making the system unworkable if the separate queue's all have jobs at the
> same time
> It would be logical that you can also set a maximum parallel overall for all
> queue's combined. Is there a reason that this is not already the case? Would
> there be anything against building this in?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
