[
https://issues.apache.org/jira/browse/SLING-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990775#comment-15990775
]
Carsten Ziegeler commented on SLING-6797:
-----------------------------------------
[~chetanm] If at all this would be a new feature - however if you already have
different types of instances (renderers vs processors) then these will
potentially issue different scheduled jobs. So you'll most probably already
solve this at the provisioning level of the instance - which I believe is a
much better place anyway
> 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)
