Modified:
websites/staging/slider/trunk/content/docs/slider_specs/canonical_scenarios.html
==============================================================================
---
websites/staging/slider/trunk/content/docs/slider_specs/canonical_scenarios.html
(original)
+++
websites/staging/slider/trunk/content/docs/slider_specs/canonical_scenarios.html
Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,9 +196,9 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-guidelines-for-clients-and-client-applications">Apache
Slider Guidelines for Clients and Client Applications</h1>
+<h1 id="apache-slider-guidelines-for-clients-and-client-applications">Apache
Slider Guidelines for Clients and Client Applications<a class="headerlink"
href="#apache-slider-guidelines-for-clients-and-client-applications"
title="Permanent link">¶</a></h1>
<p>This document will define the canonical scenarios for the deployment and
management of Slider hosted applications. It will define the types of
applications supported, the sequence of events for deploying the application
types, and the management facilities exposed for the deployed applications.</p>
-<h2 id="deployable-application-types">Deployable Application Types</h2>
+<h2 id="deployable-application-types">Deployable Application Types<a
class="headerlink" href="#deployable-application-types" title="Permanent
link">¶</a></h2>
<p>The server-side components of an application (alternatively referred to as
the application components) will be deployed and managed using a fairly uniform
mechanism. However, applications can be distinguished by their associated
client implementation. Specifically, each different client application type
can yield different development, deployment, and management approaches. There
are two primary application client types:</p>
<ol>
<li>
@@ -203,9 +214,9 @@ Latest release: <strong>0.80.0-incubatin
<p>A client that can be enhanced - a client that can have its code altered can
leverage a number of mechanisms (REST APIs, Zookeeper, a provided client
discover API) to obtain the information required to invoke the master
components of the application.</p>
</li>
</ol>
-<h2 id="deployment-scenarios">Deployment Scenarios</h2>
+<h2 id="deployment-scenarios">Deployment Scenarios<a class="headerlink"
href="#deployment-scenarios" title="Permanent link">¶</a></h2>
<p>There are two primary deployment mechanisms to examine: application
component and client-side (application client) component deployment.</p>
-<h2 id="application-component-deployment">Application Component Deployment</h2>
+<h2 id="application-component-deployment">Application Component Deployment<a
class="headerlink" href="#application-component-deployment" title="Permanent
link">¶</a></h2>
<p>Applications generally are composed of one or more components. In the
deployment steps below, be advised that there may be a need to repeat some of
the configuration/definition steps for each component.</p>
<p>The process of deploying applications (specifically, the non-client
components of an application) is:</p>
<ol>
@@ -279,7 +290,7 @@ Latest release: <strong>0.80.0-incubatin
<p>Some properties important for facilitating remote interaction with the
deployed components are advertised via zookeeper (though this may actually take
place during component start up as the assignment of ports is a late-binding
operation. Alternatively, developers may be encouraged to store these values
in a registry rather than as direct-application configuration properties).</p>
</li>
</ol>
-<h2 id="client-application-deployment">Client Application Deployment</h2>
+<h2 id="client-application-deployment">Client Application Deployment<a
class="headerlink" href="#client-application-deployment" title="Permanent
link">¶</a></h2>
<p>Although application clients are components that are deployed using
mechanisms similar to other application components (especially in the managed
case), there are a number of features that distinguish them:</p>
<ol>
<li>
@@ -300,7 +311,7 @@ Figure 1 - Managed Application Client an
</ul>
<p><img alt="Image" src="../images/unmanaged_client.png" />
Figure 2 - Unmanaged Application Client and associated Slider Application</p>
-<h3 id="managed-application-client">Managed Application Client</h3>
+<h3 id="managed-application-client">Managed Application Client<a
class="headerlink" href="#managed-application-client" title="Permanent
link">¶</a></h3>
<p>A managed application client is a component defined as part of the
Slider/yarn application (i.e. it is part of the application definition
presented to Slider). As such, it is deployed and managed via standard
Slider/yarn mechanisms. This type of application client is more than likely
already configured and written to work in a yarn environment.</p>
<p>There are two primary needs to be met for a properly functioning client:</p>
<ol>
@@ -312,11 +323,11 @@ Figure 2 - Unmanaged Application Client
</li>
</ol>
<p>Whether ascertained via discovery or bulk configuration retrieval, the
attributes that the client obtains will more than likely need to be populated
into the clientâs configuration files. Therefore, a templating facility or
the like should be provided to allow for such configuration file
manipulation.</p>
-<h3 id="unmanaged-application-client">Unmanaged Application Client</h3>
+<h3 id="unmanaged-application-client">Unmanaged Application Client<a
class="headerlink" href="#unmanaged-application-client" title="Permanent
link">¶</a></h3>
<p>An unmanaged application client is a standalone application that leverages
application components deployed into the Slider/yarn environment. It is not
possible to predict the deployment mechanisms or network topology employed for
an unmanaged application. However, it is feasible to provide some guidance
and/or software (APIs etc) to allow for application component discovery and
communication.</p>
-<h2 id="application-management">Application Management</h2>
+<h2 id="application-management">Application Management<a class="headerlink"
href="#application-management" title="Permanent link">¶</a></h2>
<p>Post deployment, the Slider infrastructure will provide the requisite set
of administrative facilities required for application management, including the
ability to start/stop the application, monitor the application, and reconfigure
the application. </p>
-<h3 id="general-management">General Management</h3>
+<h3 id="general-management">General Management<a class="headerlink"
href="#general-management" title="Permanent link">¶</a></h3>
<p>There is one general management command:</p>
<ul>
<li>
@@ -335,7 +346,7 @@ Figure 2 - Unmanaged Application Client
<p>components/roles and associated configuration</p>
</li>
</ul>
-<h3 id="applicationcomponent-management">Application/Component Management</h3>
+<h3 id="applicationcomponent-management">Application/Component Management<a
class="headerlink" href="#applicationcomponent-management" title="Permanent
link">¶</a></h3>
<p>The following administrative functions are supported for applications:</p>
<ul>
<li>
Modified:
websites/staging/slider/trunk/content/docs/slider_specs/creating_app_definitions.html
==============================================================================
---
websites/staging/slider/trunk/content/docs/slider_specs/creating_app_definitions.html
(original)
+++
websites/staging/slider/trunk/content/docs/slider_specs/creating_app_definitions.html
Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,7 +196,7 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-apppackage">Apache Slider AppPackage</h1>
+<h1 id="apache-slider-apppackage">Apache Slider AppPackage<a
class="headerlink" href="#apache-slider-apppackage" title="Permanent
link">¶</a></h1>
<p>Slider AppPackages are a declarative definition of an application for
application management. AppPackage is not a packaging scheme for application
binaries and artifacts. Tarball, zip files, rpms etc. are available for that
purpose. Instead AppPackage includes the application binaries along with other
artifacts necessary for application management.</p>
<p>An application instance consists of several active component such as one or
more masters and several slaves. There may be a number of accompanying
processes in addition to the basic master/slave processes - lets refer to all
processes as app component instances. When run in the context of Yarn, the
application specific processes are activated within individual Yarn Container.
If you pry into an Yarn container (created through Slider) it will be apparent
as to what is the role of Slider-Agent and the actual application components.
The following image provides an high-level view. Within a container there are
at least two processes - and instance of a slider agent and an instance of an
application component. The application can itself spawn more procsses if
needed.</p>
<p><img alt="Image" src="../../images/slider-container.png?raw=true" /></p>
@@ -198,7 +209,7 @@ Latest release: <strong>0.80.0-incubatin
<p>The above list shows three processes, the Slider-Agent process, the bash
script to start HBase Region Server and the HBase Region server itself.
<em>Three of these together constitute the container</em>. </p>
-<h2 id="using-an-apppackage">Using an AppPackage</h2>
+<h2 id="using-an-apppackage">Using an AppPackage<a class="headerlink"
href="#using-an-apppackage" title="Permanent link">¶</a></h2>
<p>The following command creates an HBase application using the AppPackage for
HBase.</p>
<div class="codehilite"><pre> <span class="o">./</span><span
class="n">slider</span> <span class="n">create</span> <span
class="n">cl1</span> <span class="o">--</span><span class="n">template</span>
<span class="o">/</span><span class="n">work</span><span
class="o">/</span><span class="n">appConf</span><span class="p">.</span><span
class="n">json</span> <span class="o">--</span><span class="n">resources</span>
<span class="o">/</span><span class="n">work</span><span
class="o">/</span><span class="n">resources</span><span class="p">.</span><span
class="n">json</span>
</pre></div>
@@ -210,7 +221,7 @@ Latest release: <strong>0.80.0-incubatin
<li><code>--resources</code>: yarn resource requests</li>
<li>⦠other parameters are described in accompanying docs. </li>
</ul>
-<h3 id="apppackage">AppPackage</h3>
+<h3 id="apppackage">AppPackage<a class="headerlink" href="#apppackage"
title="Permanent link">¶</a></h3>
<p>The structure of an AppPackage is described at <a
href="application_package.html">AppPackage</a>.</p>
<p>In the enlistment, there are several example AppPackages:</p>
<ul>
@@ -271,11 +282,11 @@ Latest release: <strong>0.80.0-incubatin
<p>Sample <strong>resources-default.json</strong> and
<strong>appConfig-default.json</strong> files are also included in the
enlistment. These are samples and are typically tested on one node test
installations. These files are not used during the create commmand, rather the
files provided as input parameter are the ones that are used. <em>So you can
leave these files as is in the package.</em></p>
-<h3 id="-template-appconfigjson"><code>--template appConfig.json</code></h3>
+<h3 id="-template-appconfigjson"><code>--template appConfig.json</code><a
class="headerlink" href="#-template-appconfigjson" title="Permanent
link">¶</a></h3>
<p>An appConfig.json contains the application configuration. See <a
href="application_instance_configuration.html">Specifications
InstanceConfiguration</a> for details on how to create a template config file.
The enlistment includes sample config files for HBase, Accumulo, and Storm.</p>
-<h3 id="-resources-resourcesjson"><code>--resources resources.json</code></h3>
+<h3 id="-resources-resourcesjson"><code>--resources resources.json</code><a
class="headerlink" href="#-resources-resourcesjson" title="Permanent
link">¶</a></h3>
<p>Resource specification is an input to Slider to specify the Yarn resource
needs for each component type that belong to the application. <a
href="/docs/configuration/resources.html">Specification of Resources</a>
describes how to write a resource config json file. The enlistment includes
sample config files for HBase, Accumulo, and Storm.</p>
-<h2 id="scripting-for-apppackage">Scripting for AppPackage</h2>
+<h2 id="scripting-for-apppackage">Scripting for AppPackage<a
class="headerlink" href="#scripting-for-apppackage" title="Permanent
link">¶</a></h2>
<p>Refer to <a href="writing_app_command_scripts">App Command Scripts</a> for
details on how to write scripts for a AppPackage. These scripts are in the
package/script folder within the AppPackage. <em>Use the checked in samples for
HBase/Storm/Accumulo as reference for script development.</em></p>
</div>
Modified:
websites/staging/slider/trunk/content/docs/slider_specs/hello_world_slider_app.html
==============================================================================
---
websites/staging/slider/trunk/content/docs/slider_specs/hello_world_slider_app.html
(original)
+++
websites/staging/slider/trunk/content/docs/slider_specs/hello_world_slider_app.html
Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,9 +196,9 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="goal">Goal</h1>
+<h1 id="goal">Goal<a class="headerlink" href="#goal" title="Permanent
link">¶</a></h1>
<p>Define the Slider application package for YARN hosted <a
href="https://code.google.com/p/jmemcache-daemon/";>jmemcached</a>. Jmemcached
is a functionally equivalent java implementation of memcached, a distributed
memory object caching system. The memcached daemons export the host/port they
are listening on.</p>
-<h2 id="basic-version">Basic version</h2>
+<h2 id="basic-version">Basic version<a class="headerlink"
href="#basic-version" title="Permanent link">¶</a></h2>
<p>The basic version of the app will allow creation of one or more memcached
daemons on custom ports. Some memory settings may be configured.</p>
<p>The structure of an app package is discussed <a
href="/docs/slider_specs/application_package.html">here</a>.</p>
<p>In this example, the application package created looks as follows:</p>
@@ -208,7 +219,7 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h2 id="step-1-create-metainfoxml">Step 1: Create metainfo.xml</h2>
+<h2 id="step-1-create-metainfoxml">Step 1: Create metainfo.xml<a
class="headerlink" href="#step-1-create-metainfoxml" title="Permanent
link">¶</a></h2>
<p>The minimal metainfo contains some information about the application (name,
comment, version), at least one component type, in this case its MEMCACHED, and
information about the tarball. More details are available <a
href="/docs/slider_specs/application_definition.html">here</a>.</p>
<div class="codehilite"><pre><span class="nt"><metainfo></span>
<span class="nt"><schemaVersion></span>2.0<span
class="nt"></schemaVersion></span>
@@ -258,7 +269,7 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h2 id="step-2-ensure-application-tarball">Step 2: Ensure application
tarball</h2>
+<h2 id="step-2-ensure-application-tarball">Step 2: Ensure application
tarball<a class="headerlink" href="#step-2-ensure-application-tarball"
title="Permanent link">¶</a></h2>
<p>Most applications release a tarball that you can download otherwise you can
create one. For this sample, we created a simple tarball that contains the cli
and core jar from jmemcached.</p>
<div class="codehilite"><pre><span class="n">tar</span> <span
class="n">tvf</span> <span class="n">jmemcached</span><span
class="o">-</span>1<span class="p">.</span>0<span class="p">.</span>0<span
class="p">.</span><span class="n">tar</span>
<span class="n">drwxr</span><span class="o">-</span><span
class="n">xr</span><span class="o">-</span><span class="n">x</span> 0 <span
class="n">smohanty</span> <span class="n">staff</span> 0 <span
class="n">Nov</span> 5 20<span class="p">:</span>22 <span class="o">./</span>
@@ -267,7 +278,7 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h2 id="step-3-create-a-default-resources-file-resourcesjson">Step 3: Create a
default resources file (resources.json)</h2>
+<h2 id="step-3-create-a-default-resources-file-resourcesjson">Step 3: Create a
default resources file (resources.json)<a class="headerlink"
href="#step-3-create-a-default-resources-file-resourcesjson" title="Permanent
link">¶</a></h2>
<p>By default all <code>resources.json</code> files must include a
<code>slider-appmaster</code> component
Add one more entry for the component <code>MEMCACHED</code> and assign a
unique priority and default number of instances. Ensure, that a suitable
default value is provided for yarn.memory. Additional details are available <a
href="/docs/configuration/resource.html">here</a>).</p>
<div class="codehilite"><pre><span class="p">{</span>
@@ -289,7 +300,7 @@ Add one more entry for the component <co
</pre></div>
-<h2 id="step-4-create-a-default-configuration-template-appconfigjson">Step 4:
Create a default configuration template (appConfig.json)</h2>
+<h2 id="step-4-create-a-default-configuration-template-appconfigjson">Step 4:
Create a default configuration template (appConfig.json)<a class="headerlink"
href="#step-4-create-a-default-configuration-template-appconfigjson"
title="Permanent link">¶</a></h2>
<p>The config template has few mandatory parameters such as </p>
<ul>
<li><code>application.def</code> - location of the application definition
package in default FS (e.g. HDFS). <em>This is where the application package is
stored.</em></li>
@@ -328,7 +339,7 @@ Add one more entry for the component <co
<p>Additional details on how to define a configuration template is <a
href="/docs/slider_specs/application_instance_configuration.html">here</a>.</p>
-<h2 id="step-5-implement-the-basic-commands">Step 5: Implement the basic
commands</h2>
+<h2 id="step-5-implement-the-basic-commands">Step 5: Implement the basic
commands<a class="headerlink" href="#step-5-implement-the-basic-commands"
title="Permanent link">¶</a></h2>
<p>All Slider applications are expected to implement
INSTALL/CONFIGURE/START/STOP/STATUS for each component. Some of the
implementations can be NOP - in our case, we will implement only INSTALL and
START and leave rest of the code as default. Note, Slider has an extensive
library that can be used to implement the commands. More details can be found
<a href="/docs/slider_specs/writing_app_command_scripts">here</a>.</p>
<p>The parameters file we will use is:</p>
<div class="codehilite"><pre><span class="n">from</span> <span
class="n">resource_management</span> <span class="n">import</span> <span
class="o">*</span>
@@ -392,7 +403,7 @@ Add one more entry for the component <co
<li>Executes the command to start jmemcached</li>
<li>Start writes the PID into a file that is used to check status of the
daemon</li>
</ul>
-<h2 id="debugging-tips">Debugging Tips</h2>
+<h2 id="debugging-tips">Debugging Tips<a class="headerlink"
href="#debugging-tips" title="Permanent link">¶</a></h2>
<p>End of the day, the above package runs the following command - post
formatting</p>
<div class="codehilite"><pre><span class="n">format</span><span
class="p">(</span>"<span class="p">{</span><span
class="n">java64_home</span><span class="p">}</span><span
class="o">/</span><span class="n">bin</span><span class="o">/</span><span
class="n">java</span> <span class="o">-</span><span class="n">Xmx</span><span
class="p">{</span><span class="n">xmx_val</span><span class="p">}</span> <span
class="o">-</span><span class="n">Xms</span><span class="p">{</span><span
class="n">xms_val</span><span class="p">}</span> <span class="o">-</span><span
class="n">classpath</span> <span class="p">{</span><span
class="n">app_root</span><span class="p">}</span><span class="o">/*</span><span
class="p">:{</span><span class="n">additional_cp</span><span class="p">}</span>
<span class="n">com</span><span class="p">.</span><span
class="n">thimbleware</span><span class="p">.</span><span
class="n">jmemcached</span><span class="p">.</span><span class="n">Main</span>
<span class="o">--</span><s
pan class="n">memory</span><span class="p">={</span><span
class="n">memory_val</span><span class="p">}</span> <span
class="o">--</span><span class="n">port</span><span class="p">={</span><span
class="n">port</span><span class="p">}</span>"<span class="p">)</span>
</pre></div>
@@ -406,7 +417,7 @@ Add one more entry for the component <co
<p>So, without Slider/YARN, one should be able to execute the command above
and see memcached up and running. It might be a better option to try the
command first to ensure that you have the right tarballs and environment to run
memcached.</p>
-<h2 id="add-on-package">Add on package</h2>
+<h2 id="add-on-package">Add on package<a class="headerlink"
href="#add-on-package" title="Permanent link">¶</a></h2>
<p>You can deploy the application with add on packages as well. Add on
packages are extension libraries, configurations, or scripts that the master
application can use. For example, HBase has Phoenix providing SQL access to it
and Ranger providing Authorization added to it. With Slider, you can deploy
HBase as the master application, and Phoenix and/or Ranger as the add on
package to it</p>
<p>To do that, you need to package your add on packages in a similar way to
the master package. For example, in order to deploy Phoenix with HBase, you
need to create an add on package as below:</p>
<div class="codehilite"><pre><span class="n">unzip</span> <span
class="o">-</span><span class="n">l</span> <span
class="s">"$@"</span> <span class="n">Phoenix</span><span
class="p">.</span><span class="n">zip</span>
Modified: websites/staging/slider/trunk/content/docs/slider_specs/index.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/slider_specs/index.html
(original)
+++ websites/staging/slider/trunk/content/docs/slider_specs/index.html Mon Nov
2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,27 +196,27 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-app-packaging">Apache Slider App Packaging</h1>
-<h2 id="introduction">Introduction</h2>
+<h1 id="apache-slider-app-packaging">Apache Slider App Packaging<a
class="headerlink" href="#apache-slider-app-packaging" title="Permanent
link">¶</a></h1>
+<h2 id="introduction">Introduction<a class="headerlink" href="#introduction"
title="Permanent link">¶</a></h2>
<p><strong>SLIDER: A collection of tools and technologies to simplify the
packaging, deployment and management of long-running applications on
YARN.</strong></p>
<ul>
<li>Availability (always-on) - YARN works with the application to ensure
recovery or restart of running application components.</li>
<li>Flexibility (dynamic scaling) - YARN provides the application with the
facilities to allow for scale-up or scale-down</li>
<li>Resource Mgmt (optimization) - YARN handles allocation of cluster
resources.</li>
</ul>
-<h2 id="terminology">Terminology</h2>
-<h3 id="apps-on-yarn">Apps on YARN</h3>
+<h2 id="terminology">Terminology<a class="headerlink" href="#terminology"
title="Permanent link">¶</a></h2>
+<h3 id="apps-on-yarn">Apps on YARN<a class="headerlink" href="#apps-on-yarn"
title="Permanent link">¶</a></h3>
<ul>
<li>Application written to run directly on YARN</li>
<li>Packaging, deployment and lifecycle management are custom built for each
application</li>
</ul>
-<h3 id="slider-apps">Slider Apps</h3>
+<h3 id="slider-apps">Slider Apps<a class="headerlink" href="#slider-apps"
title="Permanent link">¶</a></h3>
<ul>
<li>Applications deployed and managed on YARN using Slider</li>
<li>Use of slider minimizes custom code for deployment + lifecycle
management</li>
<li>Requires apps to follow Slider guidelines and packaging ("Sliderize")</li>
</ul>
-<h2 id="specifications">Specifications</h2>
+<h2 id="specifications">Specifications<a class="headerlink"
href="#specifications" title="Permanent link">¶</a></h2>
<p>Refer to <a href="hello_world_slider_app.html">Creating a Slider package
for Memcached</a> for a quick over view of how to write a Slider app.</p>
<p>Packaging enhancements: <a href="simple_pkg.html">Simplified Packaging</a>
describes a simplified version of packaging that Slider
supports for applications that do not need full capability of a Slider
application package.
Modified:
websites/staging/slider/trunk/content/docs/slider_specs/simple_pkg.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/slider_specs/simple_pkg.html
(original)
+++ websites/staging/slider/trunk/content/docs/slider_specs/simple_pkg.html Mon
Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,17 +196,17 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="simplified-application-packaging">Simplified Application Packaging</h1>
+<h1 id="simplified-application-packaging">Simplified Application Packaging<a
class="headerlink" href="#simplified-application-packaging" title="Permanent
link">¶</a></h1>
<p>An application may be a simple command as all of its dependencies are
pre-installed. In these cases creating a full application package zip file may
be too much. Similarly, applications artifacts can be organized in a folder
that the developer is continously editing while she is creating/debugging a
package. The need to zip up the package and uploading to FS explicitly can be
eliminated. The following simplifications are designed:</p>
<ul>
<li>eliminate the need for a zip package</li>
<li>only mandate a metadata file (allow json structure as well)</li>
<li>allow reading an application definition from a local folder</li>
</ul>
-<h2 id="examples">Examples</h2>
-<h2 id="a-minimal-application-specified-through-metadata">A minimal
application specified through metadata</h2>
+<h2 id="examples">Examples<a class="headerlink" href="#examples"
title="Permanent link">¶</a></h2>
+<h2 id="a-minimal-application-specified-through-metadata">A minimal
application specified through metadata<a class="headerlink"
href="#a-minimal-application-specified-through-metadata" title="Permanent
link">¶</a></h2>
<p>It is assummed that all binary dependencies are installed on the host
machines.</p>
-<h3 id="application-specification">Application specification</h3>
+<h3 id="application-specification">Application specification<a
class="headerlink" href="#application-specification" title="Permanent
link">¶</a></h3>
<p><strong>metainfo.json</strong></p>
<div class="codehilite"><pre><span class="p">{</span>
"<span class="n">schemaVersion</span>"<span class="p">:</span>
"2<span class="p">.</span>1"<span class="p">,</span>
@@ -217,14 +228,14 @@ Latest release: <strong>0.80.0-incubatin
<p><em>At this time a <code>resources.json</code> is required but there is a
plan to eliminate it by introducing default resource requirements through
slider-client.xml. A common resources.json file is specified <a
href="#sample_resources">here</a></em></p>
-<h3 id="create">create</h3>
+<h3 id="create">create<a class="headerlink" href="#create" title="Permanent
link">¶</a></h3>
<div class="codehilite"><pre><span class="n">slider</span> <span
class="n">create</span> <span class="n">memcachedmin</span> <span
class="o">--</span><span class="n">metainfo</span> <span
class="n">metainfo</span><span class="p">.</span><span class="n">json</span>
<span class="o">--</span><span class="n">resources</span> <span
class="n">resources</span><span class="p">.</span><span class="n">json</span>
</pre></div>
-<h2 id="a-minimal-application-with-exports">A minimal application with
exports</h2>
+<h2 id="a-minimal-application-with-exports">A minimal application with
exports<a class="headerlink" href="#a-minimal-application-with-exports"
title="Permanent link">¶</a></h2>
<p>It is assummed that all binary dependencies are installed on the host
machines. Application asks Slider to allocate a dynamic port and then export it
to the registry. You can use the same syntax as specified in <a
href="specifying_exports.html">specifying exports</a>.</p>
-<h3 id="application-specification_1">Application specification</h3>
+<h3 id="application-specification_1">Application specification<a
class="headerlink" href="#application-specification_1" title="Permanent
link">¶</a></h3>
<p><strong>metainfo.json</strong></p>
<div class="codehilite"><pre>{
"schemaVersion": "2.1",
@@ -270,14 +281,14 @@ The intent to get a dynamically allocate
</pre></div>
-<h3 id="create_1">create</h3>
+<h3 id="create_1">create<a class="headerlink" href="#create_1"
title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">slider</span> <span
class="n">create</span> <span class="n">memcachedmin</span> <span
class="o">--</span><span class="n">metainfo</span> <span
class="n">metainfo</span><span class="p">.</span><span class="n">json</span>
<span class="o">--</span><span class="n">resources</span> <span
class="n">resources</span><span class="p">.</span><span class="n">json</span>
<span class="o">--</span><span class="n">template</span> <span
class="n">appConfig</span><span class="p">.</span><span class="n">json</span>
</pre></div>
-<h2 id="a-application-with-libraries">A application with libraries</h2>
+<h2 id="a-application-with-libraries">A application with libraries<a
class="headerlink" href="#a-application-with-libraries" title="Permanent
link">¶</a></h2>
<p>In this case, the application requires some jars to be uploaded and be made
available locally. The application definition, in this case can be specified as
a folder and <em>uploaded</em> jars can be referred to from the app_root. At
this point, the layout is close to the .zip package except you do not need to
explicitly package it up. Slider will package the content and upload it.</p>
-<h3 id="application-specification_2">Application specification</h3>
+<h3 id="application-specification_2">Application specification<a
class="headerlink" href="#application-specification_2" title="Permanent
link">¶</a></h3>
<p><strong>metainfo.json</strong></p>
<div class="codehilite"><pre>{
"schemaVersion": "2.1",
@@ -340,12 +351,12 @@ The intent to get a dynamically allocate
</pre></div>
-<h3 id="create_2">create</h3>
+<h3 id="create_2">create<a class="headerlink" href="#create_2"
title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">slider</span> <span
class="n">create</span> <span class="n">memcachedjar</span> â<span
class="n">appdef</span> <span class="o">/</span><span class="n">usr</span><span
class="o">/</span><span class="n">work</span><span class="o">/</span><span
class="n">package</span> <span class="o">--</span><span
class="n">resources</span> <span class="n">resources</span><span
class="p">.</span><span class="n">json</span> <span class="o">--</span><span
class="n">template</span> <span class="n">appConfig</span><span
class="p">.</span><span class="n">json</span>
</pre></div>
-<h2 id="common-resourcesjson"><a name="sample_resources"></a> Common
resources.json</h2>
+<h2 id="common-resourcesjson"><a name="sample_resources"></a> Common
resources.json<a class="headerlink" href="#common-resourcesjson"
title="Permanent link">¶</a></h2>
<p>Here is the common resources json file for all samples.</p>
<p><strong>resources.json</strong></p>
<div class="codehilite"><pre><span class="p">{</span>
Modified:
websites/staging/slider/trunk/content/docs/slider_specs/specifying_exports.html
==============================================================================
---
websites/staging/slider/trunk/content/docs/slider_specs/specifying_exports.html
(original)
+++
websites/staging/slider/trunk/content/docs/slider_specs/specifying_exports.html
Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,20 +196,20 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="exporting-data-using-slider-app-package">Exporting data using Slider
app package</h1>
+<h1 id="exporting-data-using-slider-app-package">Exporting data using Slider
app package<a class="headerlink"
href="#exporting-data-using-slider-app-package" title="Permanent
link">¶</a></h1>
<p>Slider app package allows an application instance to export data about
itself, usually to be discoverable by the clients and IT admins. The main
classes of export specified via the application package are as follows:</p>
<ul>
<li>Exporting configurations</li>
<li>Exporting URLs, host:ports, or other information constructed based on the
deployemnt context and applied configuration</li>
</ul>
<p>All exports are specified in the metadata file, <code>metainfo.xml</code>.
An export can be at the level of the application - it means there is only one
copy of this data or at the level of a component instance - there is one copy
of the data per component instance.</p>
-<h2 id="exporting-configurations">Exporting configurations</h2>
+<h2 id="exporting-configurations">Exporting configurations<a
class="headerlink" href="#exporting-configurations" title="Permanent
link">¶</a></h2>
<p>Slider application packages accept an appConfig.json file for all
application configuration supplied by the user. Any property whose name starts
with "site" are considered configuration. <a
href="application_instance_configuration.html">Specifications
InstanceConfiguration</a> describes the naming convention.</p>
-<h3 id="export-specific-configs">Export specific configs</h3>
+<h3 id="export-specific-configs">Export specific configs<a class="headerlink"
href="#export-specific-configs" title="Permanent link">¶</a></h3>
<p>By default all configurations are exported (e.g.
<code>http://host1:44500/ws/v1/slider/publisher/slider/storm-site</code>). They
can be disabled by specifying
<code><exportedConfigs>None</exportedConfigs></code> under
<code><application></code>. If you want to explicitly specify what to
publish you can use comma separated named such as
<code><exportedConfigs>storm-site,another-site</exportedConfigs></code>.</p>
-<h3 id="which-component-is-responsible-for-export">Which component is
responsible for export</h3>
+<h3 id="which-component-is-responsible-for-export">Which component is
responsible for export<a class="headerlink"
href="#which-component-is-responsible-for-export" title="Permanent
link">¶</a></h3>
<p>By default an arbitrary master is chosen as the master responsible for
exporting the config. <em>What this means is that when this master is STARTED
the applied config known at that time is exported</em>. Otherwise, you can
specify which master component type should export configuration by specifying
<code><publishConfig>true</publishConfig></code> under
<code><component></code>.</p>
-<h2 id="exporting-formatted-data-at-application-instance-level">Exporting
formatted data at application instance level</h2>
+<h2 id="exporting-formatted-data-at-application-instance-level">Exporting
formatted data at application instance level<a class="headerlink"
href="#exporting-formatted-data-at-application-instance-level" title="Permanent
link">¶</a></h2>
<p>At application level one or more exportGroups can be defined where each
group can contain one or more exported name-value pairs. The sample export
group shown below exports two data items <code>app.monitor</code> and
<code>nimbus.host_port</code> for a Storm application instance.</p>
<div class="codehilite"><pre><span class="nt"><exportGroups></span>
<span class="nt"><exportGroup></span>
@@ -228,7 +239,7 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h2 id="exporting-formatted-data-at-component-instance-level">Exporting
formatted data at component instance level</h2>
+<h2 id="exporting-formatted-data-at-component-instance-level">Exporting
formatted data at component instance level<a class="headerlink"
href="#exporting-formatted-data-at-component-instance-level" title="Permanent
link">¶</a></h2>
<p>Occasionally, component instances may need to export data on a per
component instance basis. This is true if your application is a set of peers -
e.g. memcached daemons, or you may have a need for each slave component
instance to export some data. Currently, only the host name and dynamically
allocated port values can be exported.</p>
<p>A component export can be declaraed within the component definition or
along with application export group. When declared along the
<code>exportGroups</code> you also need to specify the component that is
responsible.</p>
<p>Add the export.</p>
Modified:
websites/staging/slider/trunk/content/docs/slider_specs/writing_app_command_scripts.html
==============================================================================
---
websites/staging/slider/trunk/content/docs/slider_specs/writing_app_command_scripts.html
(original)
+++
websites/staging/slider/trunk/content/docs/slider_specs/writing_app_command_scripts.html
Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,7 +196,7 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-developing-app-command-scripts">Apache Slider:
Developing App Command Scripts</h1>
+<h1 id="apache-slider-developing-app-command-scripts">Apache Slider:
Developing App Command Scripts<a class="headerlink"
href="#apache-slider-developing-app-command-scripts" title="Permanent
link">¶</a></h1>
<p>App command implementations follow a standard structure so that they can be
invoked in an uniform manner. For any command, the python scripts are invoked
as:</p>
<div class="codehilite"><pre><span class="n">python</span> <span
class="n">SCRIPT</span> <span class="n">COMMAND</span> <span
class="n">JSON_FILE</span> <span class="n">PACKAGE_ROOT</span> <span
class="n">STRUCTURED_OUT_FILE</span> <span class="n">LOG_LEVEL</span>
</pre></div>
@@ -206,7 +217,7 @@ Latest release: <strong>0.80.0-incubatin
<p><strong>Note</strong>: The above is how Slider-Agent invokes the scripts.
Its provided as a reference for developing the scripts themselves as well as a
way to test/debug the scripts.</p>
-<h2 id="structure-of-json-formatted-parameter">Structure of JSON formatted
parameter</h2>
+<h2 id="structure-of-json-formatted-parameter">Structure of JSON formatted
parameter<a class="headerlink" href="#structure-of-json-formatted-parameter"
title="Permanent link">¶</a></h2>
<p>The parameters are organized as multi-layer name-value pairs.</p>
<div class="codehilite"><pre><span class="p">{</span>
"<span class="n">commandId</span>"<span class="p">:</span>
"<span class="n">Command</span> <span class="n">Id</span> <span
class="n">as</span> <span class="n">assigned</span> <span class="n">by</span>
<span class="n">Slider</span>"<span class="p">,</span>
@@ -238,7 +249,7 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h3 id="sample-configuration-parameters">Sample configuration parameters</h3>
+<h3 id="sample-configuration-parameters">Sample configuration parameters<a
class="headerlink" href="#sample-configuration-parameters" title="Permanent
link">¶</a></h3>
<p>While a script can access all the config parameters the key property bags
are <strong>hostLevelParams</strong> and <strong>configurations</strong>.</p>
<div class="codehilite"><pre>{
"roleCommand": "START",
@@ -318,7 +329,7 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h2 id="command-scripts">Command scripts</h2>
+<h2 id="command-scripts">Command scripts<a class="headerlink"
href="#command-scripts" title="Permanent link">¶</a></h2>
<p>A command script essentially implements commands. The basic structure of a
script is as follows:</p>
<div class="codehilite"><pre><span class="n">class</span> <span
class="n">HbaseMaster</span><span class="p">(</span><span
class="n">Script</span><span class="p">):</span>
<span class="n">def</span> <span class="n">install</span><span
class="p">(</span><span class="n">self</span><span class="p">,</span> <span
class="n">env</span><span class="p">):</span>
@@ -356,7 +367,7 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h3 id="sample-command-script">Sample command script</h3>
+<h3 id="sample-command-script">Sample command script<a class="headerlink"
href="#sample-command-script" title="Permanent link">¶</a></h3>
<p>In this example, hbase master command implementation is using the above
parameter file and calling into several helper functions. Some are provided by
Slider (e.g. install_package, check_process_status) and some are developed for
HBase (e.g. habse_service called by start)</p>
<div class="codehilite"><pre><span class="n">class</span> <span
class="n">HbaseMaster</span><span class="p">(</span><span
class="n">Script</span><span class="p">):</span>
<span class="n">def</span> <span class="n">install</span><span
class="p">(</span><span class="n">self</span><span class="p">,</span> <span
class="n">env</span><span class="p">):</span>
Modified: websites/staging/slider/trunk/content/docs/ssl.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/ssl.html (original)
+++ websites/staging/slider/trunk/content/docs/ssl.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
@@ -182,7 +193,7 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License. See accompanying LICENSE file.
-->
-<h1
id="set-up-two-way-ssl-between-the-slider-agents-and-the-application-master">Set
Up Two-Way SSL Between the Slider Agents and the Application Master</h1>
+<h1
id="set-up-two-way-ssl-between-the-slider-agents-and-the-application-master">Set
Up Two-Way SSL Between the Slider Agents and the Application Master<a
class="headerlink"
href="#set-up-two-way-ssl-between-the-slider-agents-and-the-application-master"
title="Permanent link">¶</a></h1>
<p>Two-way SSL provides a higher level of secure communication between the
Slider Application Master and Agents by requiring both to verify each other's
identify prior to the exchange of HTTP requests and responses. By default the
communication mechanism between the two is One-Way SSL. To enable Two-way
SSL:</p>
<ul>
<li>Edit the application configuration file for the application you intend to
deploy</li>
Modified: websites/staging/slider/trunk/content/docs/troubleshooting.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/troubleshooting.html (original)
+++ websites/staging/slider/trunk/content/docs/troubleshooting.html Mon Nov 2
17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,12 +196,12 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-troubleshooting">Apache Slider Troubleshooting</h1>
+<h1 id="apache-slider-troubleshooting">Apache Slider Troubleshooting<a
class="headerlink" href="#apache-slider-troubleshooting" title="Permanent
link">¶</a></h1>
<p>Slider can be tricky to start using, because it combines the need to set
up a YARN application, with the need to have an HBase configuration
that works</p>
-<h2 id="common-problems">Common problems</h2>
-<h3
id="slider-instances-not-being-able-to-create-registry-paths-on-secure-clusters">Slider
instances not being able to create registry paths on secure clusters</h3>
+<h2 id="common-problems">Common problems<a class="headerlink"
href="#common-problems" title="Permanent link">¶</a></h2>
+<h3
id="slider-instances-not-being-able-to-create-registry-paths-on-secure-clusters">Slider
instances not being able to create registry paths on secure clusters<a
class="headerlink"
href="#slider-instances-not-being-able-to-create-registry-paths-on-secure-clusters"
title="Permanent link">¶</a></h3>
<p>This feature requires the YARN Resource Manager to do the setup securely of
the user's path in the registry</p>
<ol>
@@ -198,7 +209,7 @@ the user's path in the registry</p>
Apache Hadoop 2.6.0; it is in HDP-2.2.</li>
<li>The registry must be enabled</li>
</ol>
-<h3
id="application-instantiation-fails-triggerclusterteardownexception-unstable-cluster">Application
Instantiation fails, "TriggerClusterTeardownException: Unstable Cluster"</h3>
+<h3
id="application-instantiation-fails-triggerclusterteardownexception-unstable-cluster">Application
Instantiation fails, "TriggerClusterTeardownException: Unstable Cluster"<a
class="headerlink"
href="#application-instantiation-fails-triggerclusterteardownexception-unstable-cluster"
title="Permanent link">¶</a></h3>
<p>Slider gives up if it cannot keep enough instances of a role running -or
more
precisely, if they keep failing. </p>
<p>If this happens on cluster startup, it means that the application is not
working</p>
@@ -223,7 +234,7 @@ you may be able to grab the logs from it
Note: the URL depends on yarn.log.server.url being properly configured.</p>
<p>It is from those logs that the cause of the problem -because they are the
actual
output of the actual application which Slider is trying to deploy.</p>
-<h3
id="not-all-the-containers-start-but-whenever-you-kill-one-another-one-comes-up">Not
all the containers start -but whenever you kill one, another one comes up.</h3>
+<h3
id="not-all-the-containers-start-but-whenever-you-kill-one-another-one-comes-up">Not
all the containers start -but whenever you kill one, another one comes up.<a
class="headerlink"
href="#not-all-the-containers-start-but-whenever-you-kill-one-another-one-comes-up"
title="Permanent link">¶</a></h3>
<p>This is often caused by YARN not having enough capacity in the cluster to
start
up the requested set of containers. The AM has submitted a list of container
requests to YARN, but only when an existing container is released or killed
@@ -256,7 +267,7 @@ to schedule more role instances than it
<p>If you create too many instances, your hosts will start swapping and
performance will collapse -we do not recommend using this in production.</p>
-<h3 id="configuring-yarn-for-better-debugging">Configuring YARN for better
debugging</h3>
+<h3 id="configuring-yarn-for-better-debugging">Configuring YARN for better
debugging<a class="headerlink" href="#configuring-yarn-for-better-debugging"
title="Permanent link">¶</a></h3>
<p>One configuration to aid debugging is tell the nodemanagers to
keep data for a short period after containers finish</p>
<div class="codehilite"><pre><span class="c"><!-- 10 minutes after a
failure to see what is left in the directory--></span>
@@ -278,7 +289,7 @@ server (usually by <code>ssh</code>) and
</pre></div>
-<h3 id="running-hbase-shell-wrapper">Running HBase Shell wrapper</h3>
+<h3 id="running-hbase-shell-wrapper">Running HBase Shell wrapper<a
class="headerlink" href="#running-hbase-shell-wrapper" title="Permanent
link">¶</a></h3>
<p>We have provided an HBase Shell wrapper, hbase-slider, to facilitate
running shell commands without retrieving hbase-site.xml manually.</p>
<p>You can unpack the following scripts from hbase app package:</p>
Modified: websites/staging/slider/trunk/content/downloads/index.html
==============================================================================
--- websites/staging/slider/trunk/content/downloads/index.html (original)
+++ websites/staging/slider/trunk/content/downloads/index.html Mon Nov 2
17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,9 +196,9 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-incubating-downloads">Apache Slider (incubating)
Downloads</h1>
+<h1 id="apache-slider-incubating-downloads">Apache Slider (incubating)
Downloads<a class="headerlink" href="#apache-slider-incubating-downloads"
title="Permanent link">¶</a></h1>
<p>Be sure to verify your downloads by these <a
href="https://www.apache.org/info/verification.html";
title="Verify">procedures</a> using these <a
href="https://www.apache.org/dist/incubator/slider/KEYS";
title="KEYS">KEYS</a>.</p>
-<h2 id="current-release">Current Release</h2>
+<h2 id="current-release">Current Release<a class="headerlink"
href="#current-release" title="Permanent link">¶</a></h2>
<p>The latest release of Apache Slider™ can be
<a href="http://www.apache.org/dyn/closer.cgi/incubator/slider/";>downloaded
from the ASF</a></p>
<p>The Maven/Ivy/Gradle downloadable JAR files are published via the ASF
Modified: websites/staging/slider/trunk/content/index.html
==============================================================================
--- websites/staging/slider/trunk/content/index.html (original)
+++ websites/staging/slider/trunk/content/index.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,7 +196,7 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-dynamic-yarn-applications">Apache Slider: Dynamic YARN
Applications</h1>
+<h1 id="apache-slider-dynamic-yarn-applications">Apache Slider: Dynamic YARN
Applications<a class="headerlink"
href="#apache-slider-dynamic-yarn-applications" title="Permanent
link">¶</a></h1>
<p>Apache Slider is a YARN application to deploy existing distributed
applications on YARN,
monitor them and make them larger or smaller as desired -even while
the application is running.</p>
@@ -227,7 +238,7 @@ and later restarted.</p>
<p>Slider implements all its functionality through YARN APIs and the existing
application shell scripts. The goal of the application was to have minimal
code changes and as of this writing, it has required few changes.</p>
-<h2 id="using">Using</h2>
+<h2 id="using">Using<a class="headerlink" href="#using" title="Permanent
link">¶</a></h2>
<ul>
<li><a href="/docs/getting_started.html">Getting Started</a></li>
<li><a href="/docs/manpage.html">Man Page</a></li>
@@ -242,10 +253,10 @@ code changes and as of this writing, it
<li><a href="/docs/troubleshooting.html">Troubleshooting</a></li>
<li><a href="/docs/api/index.html">REST API</a></li>
</ul>
-<h2 id="developing">Developing</h2>
+<h2 id="developing">Developing<a class="headerlink" href="#developing"
title="Permanent link">¶</a></h2>
<p>Slider is an open source project, we encourage and welcome development.</p>
<p>Start with the <a href="developing/index.html">Developing</a> section in
the documents</p>
-<h2 id="design">Design</h2>
+<h2 id="design">Design<a class="headerlink" href="#design" title="Permanent
link">¶</a></h2>
<ul>
<li><a href="/design/architecture.html">Overview</a></li>
<li><a href="/docs/slider_specs/application_needs.html">Application
Needs</a></li>
@@ -254,7 +265,7 @@ code changes and as of this writing, it
<li><a href="/design/ssl_implementation.html">SSL Implementation</a> </li>
<li><a href="/design/rolehistory.html">Role History</a></li>
</ul>
-<h2 id="disclaimer">Disclaimer</h2>
+<h2 id="disclaimer">Disclaimer<a class="headerlink" href="#disclaimer"
title="Permanent link">¶</a></h2>
<p>Apache Slider (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the name of Apache TLP
sponsor. Incubation is required of all newly accepted projects until a
Modified: websites/staging/slider/trunk/content/mailing_lists.html
==============================================================================
--- websites/staging/slider/trunk/content/mailing_lists.html (original)
+++ websites/staging/slider/trunk/content/mailing_lists.html Mon Nov 2
17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,7 +196,7 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-mailing-lists">Apache Slider Mailing Lists</h1>
+<h1 id="apache-slider-mailing-lists">Apache Slider Mailing Lists<a
class="headerlink" href="#apache-slider-mailing-lists" title="Permanent
link">¶</a></h1>
<p>These are the mailing lists that have been established for this project.
For each list, there is a subscribe, unsubscribe, and an archive link.</p>
<table class="table table-striped">
<tr>
Modified:
websites/staging/slider/trunk/content/release_notes/release-0.30.0.html
==============================================================================
--- websites/staging/slider/trunk/content/release_notes/release-0.30.0.html
(original)
+++ websites/staging/slider/trunk/content/release_notes/release-0.30.0.html Mon
Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,19 +196,19 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-release-0300-incubating">Apache Slider Release 0.30.0
(incubating)</h1>
+<h1 id="apache-slider-release-0300-incubating">Apache Slider Release 0.30.0
(incubating)<a class="headerlink" href="#apache-slider-release-0300-incubating"
title="Permanent link">¶</a></h1>
<p>May 2014</p>
<p>This release is built against the Apache Hadoop 2.4.0, HBase-0.98.1
and Accumulo 1.5.1 artifacts. </p>
<p>Download: <a href=""></a></p>
-<h2 id="key-changes">Key changes</h2>
+<h2 id="key-changes">Key changes<a class="headerlink" href="#key-changes"
title="Permanent link">¶</a></h2>
<ol>
<li>Slider application registry that allow registration and discovery of
application configuration and URLs (such as jmx endpoints and management UI)
for client consumption.</li>
<li>Move to a .zip packaging for Slider application packages.</li>
<li>Richer metainfo support to provide start ordering and arbitrary template
that can be published.</li>
<li>Updated application definition packages for HBase, Accumulo, and Storm.
</li>
</ol>
-<h2 id="other-changes">Other changes</h2>
+<h2 id="other-changes">Other changes<a class="headerlink"
href="#other-changes" title="Permanent link">¶</a></h2>
<ol>
<li><a href="https://issues.apache.org/jira/browse/SLIDER-13";>SLIDER-13</a>
switch build to be java7+ only.</li>
</ol>
Modified:
websites/staging/slider/trunk/content/release_notes/release-0.40.0.html
==============================================================================
--- websites/staging/slider/trunk/content/release_notes/release-0.40.0.html
(original)
+++ websites/staging/slider/trunk/content/release_notes/release-0.40.0.html Mon
Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,12 +196,12 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-release-0400-incubating">Apache Slider Release 0.40.0
(incubating)</h1>
+<h1 id="apache-slider-release-0400-incubating">Apache Slider Release 0.40.0
(incubating)<a class="headerlink" href="#apache-slider-release-0400-incubating"
title="Permanent link">¶</a></h1>
<p>July 2014</p>
<p>This release is built against the Apache Hadoop 2.4.0, HBase-0.98.3
and Accumulo 1.5.1 artifacts. </p>
<p>Download: <a href=""></a></p>
-<h2 id="key-changes">Key changes</h2>
+<h2 id="key-changes">Key changes<a class="headerlink" href="#key-changes"
title="Permanent link">¶</a></h2>
<ol>
<li>Slider AppMaster and Agent communication can now be secured via 2-way
SSL.</li>
<li>Default application isolation through default HDFS working dir and ZK
node.</li>
@@ -199,8 +210,8 @@ and Accumulo 1.5.1 artifacts. </p>
<li>slider.py is added to enable Slider usage across linux and Windows
platforms.</li>
<li>agent.ini config file for the slider-agent is now optional.</li>
</ol>
-<h2 id="other-changes">Other changes</h2>
-<h2 id="known-issues">Known Issues</h2>
+<h2 id="other-changes">Other changes<a class="headerlink"
href="#other-changes" title="Permanent link">¶</a></h2>
+<h2 id="known-issues">Known Issues<a class="headerlink" href="#known-issues"
title="Permanent link">¶</a></h2>
<ol>
<li>Slider cannot handle if YARN is configured with multiple log
directories</li>
</ol>
Modified:
websites/staging/slider/trunk/content/release_notes/release-0.50.2.html
==============================================================================
--- websites/staging/slider/trunk/content/release_notes/release-0.50.2.html
(original)
+++ websites/staging/slider/trunk/content/release_notes/release-0.50.2.html Mon
Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,10 +196,10 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-release-0502-incubating">Apache Slider Release 0.50.2
(incubating)</h1>
+<h1 id="apache-slider-release-0502-incubating">Apache Slider Release 0.50.2
(incubating)<a class="headerlink" href="#apache-slider-release-0502-incubating"
title="Permanent link">¶</a></h1>
<p>August 2014</p>
<p>This release is built against Apache Hadoop 2.4.1, HBase 0.98.4 and
Accumulo 1.6.0</p>
-<h2 id="key-changes">Key changes</h2>
+<h2 id="key-changes">Key changes<a class="headerlink" href="#key-changes"
title="Permanent link">¶</a></h2>
<ol>
<li>
<p>Slider now has an integral Chaos Monkey <a
href="https://issues.apache.org/jira/browse/SLIDER-202";>SLIDER-202</a>.
@@ -207,22 +218,22 @@ We plan to keep it Java 6-compatible unt
<a href="https://issues.apache.org/jira/browse/SLIDER-273";>SLIDER-273</a></p>
</li>
</ol>
-<h2 id="incompatible-changes">Incompatible Changes</h2>
-<h3 id="slider-77-use-a-window-for-tracking-container-failures"><a
href="https://issues.apache.org/jira/browse/SLIDER-77";>SLIDER-77</a>: use a
window for tracking container failures.</h3>
+<h2 id="incompatible-changes">Incompatible Changes<a class="headerlink"
href="#incompatible-changes" title="Permanent link">¶</a></h2>
+<h3 id="slider-77-use-a-window-for-tracking-container-failures"><a
href="https://issues.apache.org/jira/browse/SLIDER-77";>SLIDER-77</a>: use a
window for tracking container failures.<a class="headerlink"
href="#slider-77-use-a-window-for-tracking-container-failures" title="Permanent
link">¶</a></h3>
<p>Previously a simple threshold,
<code>"internal.container.failure.threshold"</code> set the
limit for the number of container failures tolerated for the life of an
application.</p>
<p>This has now been reworked to support</p>
-<h1 id="a-time-bounded-window-for-failures">a time-bounded window for
failures</h1>
-<h1 id="placement-in-resourcesjson-as-yarncontainerfailurethreshold">placement
in <code>resources.json</code> as
<code>"yarn.container.failure.threshold"</code></h1>
-<h1 id="resetchanging-during-cluster-flex">reset/changing during cluster
flex</h1>
-<h1 id="configurable-in-a-combination-of-days-hours-and-minutes">Configurable
in a combination of days, hours and minutes.</h1>
+<h1 id="a-time-bounded-window-for-failures">a time-bounded window for
failures<a class="headerlink" href="#a-time-bounded-window-for-failures"
title="Permanent link">¶</a></h1>
+<h1 id="placement-in-resourcesjson-as-yarncontainerfailurethreshold">placement
in <code>resources.json</code> as
<code>"yarn.container.failure.threshold"</code><a class="headerlink"
href="#placement-in-resourcesjson-as-yarncontainerfailurethreshold"
title="Permanent link">¶</a></h1>
+<h1 id="resetchanging-during-cluster-flex">reset/changing during cluster
flex<a class="headerlink" href="#resetchanging-during-cluster-flex"
title="Permanent link">¶</a></h1>
+<h1 id="configurable-in-a-combination-of-days-hours-and-minutes">Configurable
in a combination of days, hours and minutes.<a class="headerlink"
href="#configurable-in-a-combination-of-days-hours-and-minutes"
title="Permanent link">¶</a></h1>
<p>This is a major change âand is necessary to support long-lived
applications with
a slow failure rate, while still detecting and reacting to the situation where
many containers are failing in a short period of time.</p>
<p>Because the property name has changed, any cluster where this had been
changed from
the default (which is still five) will not pick up the changes. Please use the
new name and set the value in the global section of
<code>resources.json</code></p>
-<h2 id="other-changes">Other changes</h2>
+<h2 id="other-changes">Other changes<a class="headerlink"
href="#other-changes" title="Permanent link">¶</a></h2>
<p>The full list of completed issues is <a
href="https://issues.apache.org/jira/browse/SLIDER/fixforversion/12326949/";>visible
in the Apache JIRA</a></p>
</div>
Modified:
websites/staging/slider/trunk/content/release_notes/release-0.60.0.html
==============================================================================
--- websites/staging/slider/trunk/content/release_notes/release-0.60.0.html
(original)
+++ websites/staging/slider/trunk/content/release_notes/release-0.60.0.html Mon
Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,10 +196,10 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-release-0600-incubating">Apache Slider Release 0.60.0
(incubating)</h1>
+<h1 id="apache-slider-release-0600-incubating">Apache Slider Release 0.60.0
(incubating)<a class="headerlink" href="#apache-slider-release-0600-incubating"
title="Permanent link">¶</a></h1>
<p>November 2014</p>
<p>This release is built against Apache Hadoop 2.6.0, HBase 0.98.4 and
Accumulo 1.6.1</p>
-<h2 id="key-changes">Key changes</h2>
+<h2 id="key-changes">Key changes<a class="headerlink" href="#key-changes"
title="Permanent link">¶</a></h2>
<ul>
<li>
<p>Developed against Apache Hadoop 2.6</p>
@@ -218,11 +229,11 @@ Latest release: <strong>0.80.0-incubatin
<p>Improved diagnostics support</p>
</li>
</ul>
-<h2 id="incompatible-changes">Incompatible Changes</h2>
+<h2 id="incompatible-changes">Incompatible Changes<a class="headerlink"
href="#incompatible-changes" title="Permanent link">¶</a></h2>
<ul>
<li>Apache Hadoop versions below 2.6 are not supported</li>
</ul>
-<h2 id="other-changes">Other changes</h2>
+<h2 id="other-changes">Other changes<a class="headerlink"
href="#other-changes" title="Permanent link">¶</a></h2>
<p>The full list of completed issues is <a
href="https://issues.apache.org/jira/browse/SLIDER/fixforversion/12327198/";>visible
in the Apache JIRA</a></p>
</div>
Modified:
websites/staging/slider/trunk/content/release_notes/release-0.61.0.html
==============================================================================
--- websites/staging/slider/trunk/content/release_notes/release-0.61.0.html
(original)
+++ websites/staging/slider/trunk/content/release_notes/release-0.61.0.html Mon
Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,10 +196,10 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-release-0610-incubating">Apache Slider Release 0.61.0
(incubating)</h1>
+<h1 id="apache-slider-release-0610-incubating">Apache Slider Release 0.61.0
(incubating)<a class="headerlink" href="#apache-slider-release-0610-incubating"
title="Permanent link">¶</a></h1>
<p>2015</p>
<p>This release is built against Apache Hadoop 2.6.0, HBase 0.98.4 and
Accumulo 1.6.1</p>
-<h2 id="key-changes">Key changes</h2>
+<h2 id="key-changes">Key changes<a class="headerlink" href="#key-changes"
title="Permanent link">¶</a></h2>
<p>This is exactly the same source as in Slider 0.60.0-incubating, except
it has been packaged up and released as binary artifacts.</p>
<p>These artifacts are available on the Maven central repository under
Modified:
websites/staging/slider/trunk/content/release_notes/release-0.70.1.html
==============================================================================
--- websites/staging/slider/trunk/content/release_notes/release-0.70.1.html
(original)
+++ websites/staging/slider/trunk/content/release_notes/release-0.70.1.html Mon
Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block"
href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,21 +196,21 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-release-0701-incubating">Apache Slider Release 0.70.1
(incubating)</h1>
+<h1 id="apache-slider-release-0701-incubating">Apache Slider Release 0.70.1
(incubating)<a class="headerlink" href="#apache-slider-release-0701-incubating"
title="Permanent link">¶</a></h1>
<p><strong>March 2015</strong></p>
<p>This release is built against Apache Hadoop 2.6.0, HBase 0.98.4 and
Accumulo 1.6.1</p>
-<h2 id="key-changes">Key changes</h2>
+<h2 id="key-changes">Key changes<a class="headerlink" href="#key-changes"
title="Permanent link">¶</a></h2>
<ul>
<li></li>
</ul>
-<h2 id="incompatible-changes">Incompatible Changes</h2>
+<h2 id="incompatible-changes">Incompatible Changes<a class="headerlink"
href="#incompatible-changes" title="Permanent link">¶</a></h2>
<ul>
<li></li>
</ul>
-<h2 id="work-in-progress">Work in progress</h2>
+<h2 id="work-in-progress">Work in progress<a class="headerlink"
href="#work-in-progress" title="Permanent link">¶</a></h2>
<p>This release contains some interim work in progress, work that is not
completely
functional. </p>
-<h3 id="slider-151-rest-api"><a
href="https://issues.apache.org/jira/browse/SLIDER-151";>SLIDER-151 REST
API</a></h3>
+<h3 id="slider-151-rest-api"><a
href="https://issues.apache.org/jira/browse/SLIDER-151";>SLIDER-151 REST
API</a><a class="headerlink" href="#slider-151-rest-api" title="Permanent
link">¶</a></h3>
<p>This is intended to be a full two-way REST API offered by the Slider
Application
Master to clients. The draft design is <a
href="http://slider.incubator.apache.org/docs/api";>available on the Slider web
site</a>.</p>
<p>The 0.70.1 release contains the foundational read-only view of this API.
@@ -218,7 +229,7 @@ the Slider Application Master. This can
against the cluster, such as the <code>stop</code> operation. </p>
<p>We hope ultimately to switch to this REST API as the sole communication
mechanism between (any) client and a running Slider Application Master.</p>
-<h2 id="other-changes">Other changes</h2>
+<h2 id="other-changes">Other changes<a class="headerlink"
href="#other-changes" title="Permanent link">¶</a></h2>
<p>The full list of completed issues is <a
href="https://issues.apache.org/jira/browse/SLIDER/fixforversion/12327847";>visible
in the Apache JIRA</a></p>
</div>
