Stefan Egli created SLING-10719:
-----------------------------------
Summary: 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
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)
