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 2017/05/15 09:42:04 UTC

[jira] [Closed] (SLING-6797) Deprecate scheduling a job on a specific Sling instance

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

Carsten Ziegeler closed SLING-6797.
-----------------------------------

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