svn commit: r1621958 - /sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext

[cz...@apache.org]

Author: cziegeler
Date: Tue Sep  2 11:07:18 2014
New Revision: 1621958

URL: http://svn.apache.org/r1621958
Log:
Add runOn property

Modified:
    sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext

Modified: sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext?rev=1621958&r1=1621957&r2=1621958&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext Tue Sep  2 11:07:18 2014
@@ -68,7 +68,19 @@ By default, jobs can be concurrently exe
 
 
     @Property(name="scheduler.concurrent", boolValue=false)
-    ## The Scheduler API
+
+### Scheduling the job just once in a cluster
+
+If the same code/same services is executed on multiple nodes within a cluster, the same job might be scheduled on each instance. If this is not desired, the job can either be bound to the leader of the topology or a single instance (which one this is, is not further defined):
+  
+    @Property(name="scheduler.runOn", value="LEADER");
+
+or
+
+    @Property(name="scheduler.runOn", value="SINGLE");
+
+
+## The Scheduler API
 
 The scheduler has methods to execute jobs periodically, based on a cron expression or at a given time. For more details please refer to the [javadocs](http://sling.apache.org/apidocs/sling6/org/apache/sling/commons/scheduler/Scheduler.html).