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 2013/07/31 11:25:47 UTC
[jira] [Commented] (SLING-2979) Add support for running scheduled
task on specific instances
[ https://issues.apache.org/jira/browse/SLING-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725055#comment-13725055 ]
Carsten Ziegeler commented on SLING-2979:
-----------------------------------------
I'Ve revised the implementation and changed the property to "scheduler.runOn" which can either have
- a string (array) of Sling IDs where this job should run
- the constant LEADER - to run on the leader only
- the constant SINGLE - to run on a single instance only
> Add support for running scheduled task on specific instances
> ------------------------------------------------------------
>
> Key: SLING-2979
> URL: https://issues.apache.org/jira/browse/SLING-2979
> Project: Sling
> Issue Type: New Feature
> Components: Commons
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons Scheduler 2.4.0
>
>
> With the new topology api we have support for leader election. In many cases scheduled tasks should only run on a single instance in a cluster. So far this can only be done by manually adding the task through the Scheduler interface but not with the whiteboard support.
> We should add a new property scheduler.leaderonly which defaults to false but can be set to true. IN this case the task is only started on the leader.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira