[
https://issues.apache.org/jira/browse/SLING-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-4635.
-------------------------------------
Resolution: Fixed
Resolved as explained above. I've also changed the implementation to use the
settings service to get the Sling ID - this allows to schedule based on Sling
IDs even if topology is not available.
The web console plugin is updated to display if a job is not scheduled and why.
In addition the service id is now displayed for whiteboard registrations
> Topology related jobs shouldn't be scheduled if topology is unclear/not
> available
> ---------------------------------------------------------------------------------
>
> Key: SLING-4635
> URL: https://issues.apache.org/jira/browse/SLING-4635
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Scheduler 2.4.6
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons Scheduler 2.4.8
>
>
> If a job is scheduled to be run only on the leader or only on a single
> instance, it is currently scheduled even if the topology is not available or
> changing.
> This is wrong as this can lead to the job being scheduled more than once in a
> cluster in such situations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
