You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/06/13 18:13:00 UTC

[jira] [Closed] (SLING-4635) Topology related jobs shouldn't be scheduled if topology is unclear/not available

     [ https://issues.apache.org/jira/browse/SLING-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-4635.
-----------------------------------

> 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)