Author: buildbot
Date: Fri May 15 07:06:51 2015
New Revision: 951341
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri May 15 07:06:51 2015
@@ -1 +1 @@
-1678488
+1679505
Modified:
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
Fri May 15 07:06:51 2015
@@ -172,7 +172,7 @@
</tr>
<tr>
<td><code>queue.type</code></td>
-<td>The type of the queue: ORDERED, UNORDERED, TOPIC, ROUND-ROBIN, IGNORE,
DROP</td>
+<td>The type of the queue: ORDERED, UNORDERED, TOPIC_ROUND_ROBIN</td>
</tr>
<tr>
<td><code>queue.topics</code></td>
@@ -203,14 +203,10 @@
<p>The configurations are processed in order of their service ranking. The
first matching queue configuration is used for the job.</p>
<h4 id="ordered-queues">Ordered Queues</h4>
<p>An ordered queue processes one job after the other.</p>
-<h4 id="unordered-queues">Unordered Queues</h4>
+<h4 id="unordered-queues-or-parallel-queues">Unordered Queues (or Parallel
queues)</h4>
<p>Unordered queues process jobs in parallel.</p>
<h4 id="topic-round-robin-queues">Topic-Round-Robin Queues</h4>
<p>The jobs are processed in parallel. Scheduling of the jobs is based on the
topic of the jobs. These are started by doing round-robin on the available
topics.</p>
-<h4 id="ignoring-queues">Ignoring Queues</h4>
-<p>A queue of type <em>ignoring</em> ignores this job. The job is persisted
but not processed. This can be used to delay processing of some jobs. With a
changed configuration, the ignored jobs can be processed at a later time.</p>
-<h4 id="dropping-queues">Dropping Queues</h4>
-<p>A queue of type <em>drop</em> is dropping a job - which means it is not
processed at all and directly discarded.</p>
<h3 id="job-distributing">Job Distributing</h3>
<p>For job distribution (= distributing the processing in a cluster), the job
handling uses the topology feature from Sling - each instance in the topology
announces the set of topics (consumers) it currently has - and this defines the
job capabilities, a mapping from an instance to the topics it can process.</p>
<p>When a job is scheduled, the job manager uses these capabilities to find
out the set of instances which is able to process the request. If the queue
type is <em>ordered</em> then all jobs are processed by the leader of this set.
For parallel queues, the jobs are distributed equally amongst those
instance.</p>
@@ -236,7 +232,7 @@
<h2 id="sending-scheduled-events">Sending Scheduled Events</h2>
<p>Scheduled events are OSGi events that have been created by the environemnt.
They are generated on each application node of the cluster through an own
scheduler instance. Sending these events works the same as sending events based
on JCR events (see above).</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1619803 by cziegeler on Fri, 22 Aug 2014 13:35:49 +0000
+ Rev. 1679505 by cziegeler on Fri, 15 May 2015 07:06:36 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
