Yepp, I thought about this as well and came to the same conclusion. However, apart from the Sling ID there is today no other mechanism to identify an instance - apart from the leader. So I went with the easiest case first.
Regards Carsten 2013/7/29 Felix Meschberger <[email protected]> > Hi > > Is it really so, that a job may be run on any instance or the leader > instance ? Shouldn't we be able to bind a scheduled job just any instance X > where "LEADER" might just be a special well-known instance name (like the > HEAD revision in subversion) ? > > Regards > Felix > > Am 25.07.2013 um 15:59 schrieb Carsten Ziegeler (JIRA): > > > Carsten Ziegeler created SLING-2979: > > --------------------------------------- > > > > Summary: Scheduled task should only run on leader > > 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.3.6 > > > > > > 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 > > -- Carsten Ziegeler [email protected]
