Author: buildbot
Date: Thu Nov 26 12:36:27 2015
New Revision: 973628
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Nov 26 12:36:27 2015
@@ -1 +1 @@
-1716615
+1716617
Modified:
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
Thu Nov 26 12:36:27 2015
@@ -317,15 +317,17 @@ This is done by setting a corresponding
</ul>
<p>To avoid having each instance make it's own, perhaps differing conclusions
as to which instance/heartbeat is dead or not,
there is an explicit, unanimous voting mechanism that agrees upon a list of
alive instances. This list of alive
-instances is called cluster view.<br />
-<em> as soon as any instance notices a change in the list of active instances,
it is free to calculate a new
-such list and start a voting in the cluster - each voting carries a unique
votingId
-</em> since any instance can do this, you can have concurrent creation of new
votings
-<em> each instance has one 'yes' vote - and if there are multiple concurrent
votings the lowest one wins
-</em> when a voting receives a 'yes' from all instances that it enlists it is
considered as 'winning'
-and is promoted to be the new, valid view from now on.
-* a promoted view is stored in
<code>/var/discovery/impl/establishedView</code> and any change therein is
-passed on in a TopologyEvent to all registered listeners.</p>
+instances is called cluster view. </p>
+<ul>
+<li>as soon as any instance notices a change in the list of active instances,
it is free to calculate a new
+such list and start a voting in the cluster - each voting carries a unique
votingId</li>
+<li>since any instance can do this, you can have concurrent creation of new
votings</li>
+<li>each instance has one 'yes' vote - and if there are multiple concurrent
votings the lowest one wins</li>
+<li>when a voting receives a 'yes' from all instances that it enlists it is
considered as 'winning'
+and is promoted to be the new, valid view from now on.</li>
+<li>a promoted view is stored in
<code>/var/discovery/impl/establishedView</code> and any change therein is
+passed on in a TopologyEvent to all registered listeners.</li>
+</ul>
<h3 id="topology-connectors-for-cross-cluster-discovery">Topology Connectors
for Cross-Cluster Discovery<a class="headerlink"
href="#topology-connectors-for-cross-cluster-discovery" title="Permanent
link">¶</a></h3>
<p>From a discovery API's point of view a cluster consists of all instances
that are connected to the same repository.
The above described built-in mechanism of storing a lastHeartbeat property
into the (shared) repository, of voting on changes
@@ -399,7 +401,7 @@ They use the same interval and timeout a
</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1716615 by stefanegli on Thu, 26 Nov 2015 12:31:04 +0000
+ Rev. 1716617 by stefanegli on Thu, 26 Nov 2015 12:36:19 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
