Author: buildbot
Date: Sun Jan 10 19:00:30 2016
New Revision: 977434
Log:
Staging update by buildbot for slider
Modified:
websites/staging/slider/trunk/content/ (props changed)
websites/staging/slider/trunk/content/docs/placement.html
Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Jan 10 19:00:30 2016
@@ -1 +1 @@
-1723949
+1723951
Modified: websites/staging/slider/trunk/content/docs/placement.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/placement.html (original)
+++ websites/staging/slider/trunk/content/docs/placement.html Sun Jan 10
19:00:30 2016
@@ -214,17 +214,17 @@ the cluster. For details on the implemen
<h2 id="introduction">Introduction<a class="headerlink" href="#introduction"
title="Permanent link">¶</a></h2>
<p>A Slider Application Instance consists of the Application Master
âSlider's codeâ and
the components requested in the <code>resources.json</code> file. For each
component,
-slider requests a new YARN Container, which is then allocated in the Hadoo
cluster
+Slider requests a new YARN Container, which is then allocated in the Hadoo
cluster
by YARN. The Slider application starts the component within the container,
and monitors its lifecycle.</p>
<p>The choice of where a container is created is something in which YARN and
-slider can participate. It is up to YARN to allocate the capacity for the
+Slider can participate. It is up to YARN to allocate the capacity for the
container (CPU, memory, etc), possibly killing other containers ("pre-emption")
-to satisfy the requests submitted by slider.</p>
+to satisfy the requests submitted by Slider.</p>
<p>Slider can make different kinds of container requests of YARN</p>
<ol>
<li>
-<p><strong>Anywhere</strong>. Here slider asks YARN for a container anywhere
+<p><strong>Anywhere</strong>. Here Slider asks YARN for a container anywhere
in the cluster. These requests are most likely to be satisfied, as if there
is space anywhere in the cluster, YARN will allocate it.</p>
</li>
@@ -362,22 +362,22 @@ type are created on the same server. </p
<p>Anti-affinity placement is implemented in Slider by asking for each
instance one-by-one, requesting a container on any host with the
desired label <em>that is not running an instance of the component
type</em>.</p>
-<p>This means that slider cannot build a large application instance by
simultaneously
+<p>This means that Slider cannot build a large application instance by
simultaneously
asking for many containers of a specific component type âfor any type where
anti-affinity is required, the requests must take place one-by-one. This makes
placement significantly slower when trying to start a large application.</p>
-<p>Furthermore, the guarantee that slider Slider makes: no two instances of
+<p>Furthermore, the guarantee that Slider makes: no two instances of
a component on the same host, means that if there is no capacity in for a
container
-on any of the hosts not yet running a component instance âslider will not
+on any of the hosts not yet running a component instance âSlider will not
relax the request. </p>
<p>That is: in exchange for a guarantee of anti-affinity, you many sacrifice
the
ability to run as many instances as you request âeven if there is space in
the cluster.</p>
<p><a name="outstanding-requests"></p>
<h2 id="slider-and-outstanding-requests">Slider and "Outstanding Requests"<a
class="headerlink" href="#slider-and-outstanding-requests" title="Permanent
link">¶</a></h2>
-<p>One recurrent support problem people raise with slider is that it appears
+<p>One recurrent support problem people raise with Slider is that it appears
to hang with one or more outstanding requests. When this situation arises,
-it is not a sign that there is anything wrong with slider. It means
+it is not a sign that there is anything wrong with Slider. It means
<em>there is nowhere for YARN to allocate the desired containers</em>.</p>
<p>Here are the common causes</p>
<ul>
@@ -433,7 +433,7 @@ scratch.</p>
<h2 id="changes">Changes<a class="headerlink" href="#changes" title="Permanent
link">¶</a></h2>
<h3 id="slider-0902-incubating">Slider 0.90.2-incubating<a class="headerlink"
href="#slider-0902-incubating" title="Permanent link">¶</a></h3>
<p>Slider now supports Anti-affinity <a
href="https://issues.apache.org/jira/browse/SLIDER-82";>SLIDER-82</a></p>
-<p>This a feature regularly requested: you can now tell slider to place all
instances
+<p>This a feature regularly requested: you can now tell Slider to place all
instances
of a component on different hosts. It will attempt to do this
(iteratively),</p>
<h3 id="slider-080-incubating">Slider 0.80-incubating<a class="headerlink"
href="#slider-080-incubating" title="Permanent link">¶</a></h3>
<p>A major rework of placement has taken place, <a
href="https://issues.apache.org/jira/browse/SLIDER-611";>Ãber-JIRA : placement
phase 2</a></p>
