[
https://issues.apache.org/jira/browse/SLING-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992691#comment-15992691
]
Chetan Mehrotra commented on SLING-6797:
----------------------------------------
bq. So you'll most probably already solve this at the provisioning level of
the instance
Thinking about it yes this makes better sense. We can rely on OSGi config to
activate certain components on certain type of setups (just ensure that OSGi
config is not replicated across cluster). So we need to add support for this in
scheduler
> Deprecate scheduling a job on a specific Sling instance
> -------------------------------------------------------
>
> Key: SLING-6797
> URL: https://issues.apache.org/jira/browse/SLING-6797
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons Scheduler 2.5.4
>
>
> Currently it's possible to schedule a job on a specific instance by
> specifying the exact instance id. This feature is questionable, especially
> with instances coming and going it's hard to know the id in advance.
> It's better to rely on a good mechanism to distribute the scheduled jobs
> amongst availabe instances or use the leader
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
