[
https://issues.apache.org/jira/browse/SLING-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1790.
-------------------------------------
Resolution: Fixed
Fixed in revision 999457 - also cleaned up the event listener registration and
added some new tests
> Job handling does only use cluster for failover
> -----------------------------------------------
>
> Key: SLING-1790
> URL: https://issues.apache.org/jira/browse/SLING-1790
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Extensions Event 2.4.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.4.2
>
>
> If jobs are added in a clustered environment, they are currently only added
> on the instance where the job has been created. Therefore jobs are never load
> balanced.
> The exception is if a job fails on an instance; in this case this job is
> added to other cluster nodes.
> This is a very inconsistent behaviour and should be changed to:
> - jobs are always added to all cluster nodes (except if the run local flag is
> set)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
