[
https://issues.apache.org/jira/browse/SLING-10719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397116#comment-17397116
]
Stefan Egli commented on SLING-10719:
-------------------------------------
* [PR#14|https://github.com/apache/sling-org-apache-sling-event/pull/14] created
* [~cziegeler], would you like to review?
> Avoid reset of maxparallel jobs counting on topology change
> -----------------------------------------------------------
>
> Key: SLING-10719
> URL: https://issues.apache.org/jira/browse/SLING-10719
> Project: Sling
> Issue Type: Bug
> Components: Event
> Affects Versions: Event 4.2.22
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Major
> Fix For: Event 4.2.24
>
>
> Upon a topology change job queues are outdated and restarted. As part of
> this, the {{available}} counter (which implements the {{maxparallel}}
> feature) gets reset. Therefore if there are long-running jobs at that time,
> those jobs are as a result excluded from the counting. This can lead to more
> jobs being started/running than are configured with {{maxparallel}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
