Updated the website built from mesos SHA: f5f7ec0.

Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/59c3cef4
Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/59c3cef4
Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/59c3cef4

Branch: refs/heads/asf-site
Commit: 59c3cef4886ec07755a061361ad76778b7c94b01
Parents: 873b056
Author: jenkins <bui...@apache.org>
Authored: Mon Mar 12 07:30:40 2018 +0000
Committer: jenkins <bui...@apache.org>
Committed: Mon Mar 12 07:30:40 2018 +0000

----------------------------------------------------------------------
 content/blog/feed.xml                           |    2 +-
 .../index.html                                  |    2 +-
 .../documentation/high-availability/index.html  |    2 +-
 .../latest/high-availability/index.html         |    2 +-
 content/sitemap.xml                             | 9090 +++++++++---------
 5 files changed, 4549 insertions(+), 4549 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos-site/blob/59c3cef4/content/blog/feed.xml
----------------------------------------------------------------------
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 2cc1e6b..0d24052 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -295,7 +295,7 @@ To learn more about CSI work in Mesos, you can dig into the 
design document &lt;
 &lt;/ul&gt;
 
 
-&lt;p&gt;If you are a user and would like to suggest some areas for 
performance improvement, please let us know by emailing &lt;a 
href=&quot;&amp;#109;&amp;#x61;&amp;#105;&amp;#108;&amp;#116;&amp;#x6f;&amp;#x3a;&amp;#x64;&amp;#101;&amp;#118;&amp;#x40;&amp;#x61;&amp;#x70;&amp;#x61;&amp;#x63;&amp;#x68;&amp;#x65;&amp;#x2e;&amp;#x6d;&amp;#101;&amp;#115;&amp;#x6f;&amp;#x73;&amp;#46;&amp;#111;&amp;#114;&amp;#x67;&quot;&gt;&amp;#100;&amp;#x65;&amp;#118;&amp;#64;&amp;#x61;&amp;#112;&amp;#97;&amp;#x63;&amp;#104;&amp;#101;&amp;#46;&amp;#109;&amp;#101;&amp;#115;&amp;#x6f;&amp;#x73;&amp;#x2e;&amp;#111;&amp;#114;&amp;#x67;&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;If you are a user and would like to suggest some areas for 
performance improvement, please let us know by emailing &lt;a 
href=&quot;&amp;#109;&amp;#97;&amp;#105;&amp;#108;&amp;#116;&amp;#x6f;&amp;#x3a;&amp;#x64;&amp;#x65;&amp;#118;&amp;#x40;&amp;#x61;&amp;#x70;&amp;#x61;&amp;#x63;&amp;#x68;&amp;#101;&amp;#x2e;&amp;#x6d;&amp;#x65;&amp;#115;&amp;#111;&amp;#115;&amp;#x2e;&amp;#x6f;&amp;#114;&amp;#x67;&quot;&gt;&amp;#x64;&amp;#101;&amp;#x76;&amp;#x40;&amp;#97;&amp;#x70;&amp;#x61;&amp;#99;&amp;#104;&amp;#101;&amp;#x2e;&amp;#x6d;&amp;#x65;&amp;#x73;&amp;#111;&amp;#115;&amp;#x2e;&amp;#111;&amp;#114;&amp;#103;&lt;/a&gt;.&lt;/p&gt;
 
        </content>
   </entry>

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/59c3cef4/content/blog/performance-working-group-progress-report/index.html
----------------------------------------------------------------------
diff --git a/content/blog/performance-working-group-progress-report/index.html 
b/content/blog/performance-working-group-progress-report/index.html
index 947a896..bb41b71 100644
--- a/content/blog/performance-working-group-progress-report/index.html
+++ b/content/blog/performance-working-group-progress-report/index.html
@@ -248,7 +248,7 @@
 </ul>
 
 
-<p>If you are a user and would like to suggest some areas for performance 
improvement, please let us know by emailing <a 
href="&#109;&#x61;&#105;&#108;&#116;&#x6f;&#x3a;&#x64;&#101;&#118;&#x40;&#x61;&#x70;&#x61;&#x63;&#x68;&#x65;&#x2e;&#x6d;&#101;&#115;&#x6f;&#x73;&#46;&#111;&#114;&#x67;">&#100;&#x65;&#118;&#64;&#x61;&#112;&#97;&#x63;&#104;&#101;&#46;&#109;&#101;&#115;&#x6f;&#x73;&#x2e;&#111;&#114;&#x67;</a>.</p>
+<p>If you are a user and would like to suggest some areas for performance 
improvement, please let us know by emailing <a 
href="&#109;&#97;&#105;&#108;&#116;&#x6f;&#x3a;&#x64;&#x65;&#118;&#x40;&#x61;&#x70;&#x61;&#x63;&#x68;&#101;&#x2e;&#x6d;&#x65;&#115;&#111;&#115;&#x2e;&#x6f;&#114;&#x67;">&#x64;&#101;&#x76;&#x40;&#97;&#x70;&#x61;&#99;&#104;&#101;&#x2e;&#x6d;&#x65;&#x73;&#111;&#115;&#x2e;&#111;&#114;&#103;</a>.</p>
 
   </div>
 </div>

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/59c3cef4/content/documentation/high-availability/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/high-availability/index.html 
b/content/documentation/high-availability/index.html
index 496c6ec..387d1af 100644
--- a/content/documentation/high-availability/index.html
+++ b/content/documentation/high-availability/index.html
@@ -183,7 +183,7 @@
 
 <ul>
 <li><p>The lower level <code>LeaderContender</code> and 
<code>LeaderDetector</code> implement a generic ZooKeeper election algorithm 
loosely modeled after this
-<a 
href="http://zookeeper.apache.org/doc/trunk/recipes.html#sc_leaderElection";>recipe</a>
 (sans herd effect handling due to the master group&rsquo;s small size, which 
is often 3).</p></li>
+<a 
href="http://zookeeper.apache.org/doc/current/recipes.html#sc_leaderElection";>recipe</a>
 (sans herd effect handling due to the master group&rsquo;s small size, which 
is often 3).</p></li>
 <li><p>The higher level <code>MasterContender</code> and 
<code>MasterDetector</code> wrap around ZooKeeper&rsquo;s contender and 
detector abstractions as adapters to provide/interpret the ZooKeeper 
data.</p></li>
 <li><p>Each Mesos master simultaneously uses both a contender and a detector 
to try to elect themselves and detect who the current leader is. A separate 
detector is necessary because each master&rsquo;s WebUI redirects browser 
traffic to the current leader when that master is not elected. Other Mesos 
components (i.e., agents and scheduler drivers) use the detector to find the 
current leader and connect to it.</p></li>
 </ul>

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/59c3cef4/content/documentation/latest/high-availability/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/high-availability/index.html 
b/content/documentation/latest/high-availability/index.html
index 1a6ed5a..0e71a1f 100644
--- a/content/documentation/latest/high-availability/index.html
+++ b/content/documentation/latest/high-availability/index.html
@@ -183,7 +183,7 @@
 
 <ul>
 <li><p>The lower level <code>LeaderContender</code> and 
<code>LeaderDetector</code> implement a generic ZooKeeper election algorithm 
loosely modeled after this
-<a 
href="http://zookeeper.apache.org/doc/trunk/recipes.html#sc_leaderElection";>recipe</a>
 (sans herd effect handling due to the master group&rsquo;s small size, which 
is often 3).</p></li>
+<a 
href="http://zookeeper.apache.org/doc/current/recipes.html#sc_leaderElection";>recipe</a>
 (sans herd effect handling due to the master group&rsquo;s small size, which 
is often 3).</p></li>
 <li><p>The higher level <code>MasterContender</code> and 
<code>MasterDetector</code> wrap around ZooKeeper&rsquo;s contender and 
detector abstractions as adapters to provide/interpret the ZooKeeper 
data.</p></li>
 <li><p>Each Mesos master simultaneously uses both a contender and a detector 
to try to elect themselves and detect who the current leader is. A separate 
detector is necessary because each master&rsquo;s WebUI redirects browser 
traffic to the current leader when that master is not elected. Other Mesos 
components (i.e., agents and scheduler drivers) use the detector to find the 
current leader and connect to it.</p></li>
 </ul>

Reply via email to