[
https://issues.apache.org/jira/browse/SLING-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502552#comment-14502552
]
Carsten Ziegeler commented on SLING-4635:
-----------------------------------------
The problem is, that right now the discovery (api) is treated as optional. The
scheduler works without it. However scheduling of the above menitoned features
makes only sense if discovery is available.
Therefore we should:
a) if no discovery is available, log an error - and no scheduling
b) if discovery is available, but no stable view is available, log in debug -
and no scheduling
c) if discovery is available, and view is stable, schedule accordingly
> 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)
