You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2017/03/01 14:02:01 UTC
svn commit: r1007503 - in /websites/staging/sling/trunk/content: ./
documentation/bundles/discovery-api-and-impl.html
Author: buildbot
Date: Wed Mar 1 14:02:01 2017
New Revision: 1007503
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 Wed Mar 1 14:02:01 2017
@@ -1 +1 @@
-1784934
+1784944
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 Wed Mar 1 14:02:01 2017
@@ -353,7 +353,9 @@ first send a TOPOLOGY_CHANGING event to
and then start a new voting. Once the voting concludes a TOPOLOGY_CHANGED event will follow.</p>
<p>Given the voting is happening through the repository as well, one could imagine a situation where the repository delays
can cause a topology to be "pseudo partitioned" into two or more parts, each one agreeing on a set of instances in that
-sub-cluster. Such a situation would only last as long as the repository delays are large (larger than
+sub-cluster (one requirement for such a scenario being that the delays must be asymmetric, ie changes from a subset
+of instances propagate slow, while the remaining changes propagate fast - ie. two different sets of delays in the cluster).
+Such a situation would only last as long as the repository delays are large (larger than
the heartbeat timeouts). Exact cases where the repository experiences large delays depend of course on the
repository configuration and deployment details, known cases include for example long running queries, large set
of changes, large set of commits and long-running session.saves.</p>
@@ -502,7 +504,7 @@ cross-cluster topology announcements (vi
<p>This is the base bundle solely used by discovery.impl and discovery.oak and contains exactly the mentioned
properties and announcement handling.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1784934 by stefanegli on Wed, 1 Mar 2017 13:54:18 +0000
+ Rev. 1784944 by stefanegli on Wed, 1 Mar 2017 14:01:53 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project