Author: buildbot
Date: Wed Oct 15 16:50:03 2014
New Revision: 925872
Log:
Staging update by buildbot for slider
Modified:
websites/staging/slider/trunk/content/ (props changed)
websites/staging/slider/trunk/content/developing/testing.html
websites/staging/slider/trunk/content/docs/client-configuration.html
websites/staging/slider/trunk/content/docs/exitcodes.html
websites/staging/slider/trunk/content/docs/manpage.html
Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Oct 15 16:50:03 2014
@@ -1 +1 @@
-1631012
+1632119
Modified: websites/staging/slider/trunk/content/developing/testing.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/testing.html (original)
+++ websites/staging/slider/trunk/content/developing/testing.html Wed Oct 15
16:50:03 2014
@@ -250,7 +250,7 @@ AM and spawned processeses run independe
<span class="nt"><property></span>
<span class="nt"><name></span>hadoop.home<span
class="nt"></name></span>
- <span class="nt"><value></span>/home/slider/hadoop-2.2.0<span
class="nt"></value></span>
+ <span class="nt"><value></span>/home/slider/hadoop-2.6.0<span
class="nt"></value></span>
<span class="nt"><description></span>Hadoop home dir on target
systems<span class="nt"></description></span>
<span class="nt"></property></span>
@@ -263,6 +263,23 @@ all the values. </p>
<p>For the functional tests, the accumulo and hbase tar properties will
need to be set to a URL of a tar file that is accessible to all the
nodes in the cluster -which usually means HDFS, and so an <code>hdfs://</code>
URL</p>
+<h2 id="security">Security</h2>
+<div class="codehilite"><pre><span class="nt"><property></span>
+ <span class="nt"><name></span>slider.am.login.keytab.name<span
class="nt"></name></span>
+ <span class="nt"><value></value></span>
+<span class="nt"></property></span>
+<span class="nt"><property></span>
+ <span class="nt"><name></span>slider.am.keytab.local.path<span
class="nt"></name></span>
+ <span class="nt"><description></span>absolute path to keytab<span
class="nt"></description></span>
+ <span class="nt"><value></value></span>
+<span class="nt"></property></span>
+<span class="nt"><property></span>
+ <span class="nt"><name></span>slider.keytab.principal.name<span
class="nt"></name></span>
+ <span class="nt"><value></value></span>
+<span class="nt"></property></span>
+</pre></div>
+
+
<h2 id="provider-specific-parameters">Provider-specific parameters</h2>
<p>An individual provider can pick up settings from their own
<code>src/test/resources/slider-client.xml</code> file, or the one in
<code>slider-core</code>.
Modified: websites/staging/slider/trunk/content/docs/client-configuration.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/client-configuration.html
(original)
+++ websites/staging/slider/trunk/content/docs/client-configuration.html Wed
Oct 15 16:50:03 2014
@@ -344,15 +344,6 @@ a limited number of slider-specific conf
</pre></div>
-<h3
id="sliderzookeeperquorum-the-zookeeper-quorum"><code>slider.zookeeper.quorum</code>
- the zookeeper quorum.</h3>
-<p>This defines the zookeeper quorum for this YARN cluster. </p>
-<p>It is used to locate the service registry, enable running instances to
publish
-information about their application, and for clients to query this. </p>
-<p>It is also used as the default zookeeper binding for any application that
-uses zookeeper in its configuration -the value set when the application is
-defined will be copied into the instance definition file.</p>
-<h3
id="sliderregistrypath-the-zookeeper-path-for-the-service-registry"><code>"slider.registry.path"</code>
- the zookeeper path for the service registry</h3>
-<p>This declares the the zookeeper path for the service registry. </p>
<h3
id="slideryarnrestartlimit-set-limit-on-application-master-restarts"><code>slider.yarn.restart.limit</code>
- set limit on Application Master Restarts</h3>
<p>This limits how many times YARN should start a failed application
master.</p>
<p>A short restart limit is useful when initially creating a cluster, as it
@@ -399,6 +390,19 @@ that contains the application data <code
</pre></div>
+<h2 id="yarn-registry-binding">YARN Registry binding</h2>
+<p>Slider uses the (evolving) YARN service registry to register application
+instances, to locate them, and as a means to publish the configuration
information
+needed to connect to the slider-deployed applications.</p>
+<h3
id="sliderzookeeperquorum-the-zookeeper-quorum"><code>slider.zookeeper.quorum</code>
- the zookeeper quorum.</h3>
+<p>This defines the zookeeper quorum for this YARN cluster. </p>
+<p>It is used to locate the service registry, enable running instances to
publish
+information about their application, and for clients to query this. </p>
+<p>It is also used as the default zookeeper binding for any application that
+uses zookeeper in its configuration -the value set when the application is
+defined will be copied into the instance definition file.</p>
+<h3
id="sliderregistrypath-the-zookeeper-path-for-the-service-registry"><code>"slider.registry.path"</code>
- the zookeeper path for the service registry</h3>
+<p>This declares the the zookeeper path for the service registry. </p>
<h2 id="debugging-configuration-issues">Debugging configuration issues</h2>
<p>If the slider packages are set to log at debug level in the log4j
configuration
file, details on properties will be part of the copious output.</p>
Modified: websites/staging/slider/trunk/content/docs/exitcodes.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/exitcodes.html (original)
+++ websites/staging/slider/trunk/content/docs/exitcodes.html Wed Oct 15
16:50:03 2014
@@ -282,7 +282,7 @@ no. 72.</p>
<span class="k">int</span> <span class="no">EXIT_PROCESS_FAILED</span> <span
class="o">=</span> <span class="mh">72</span><span class="p">;</span>
<span class="cm">/**</span>
-<span class="cm"> * The cluster failed -too many containers were</span>
+<span class="cm"> * The instance could not be deployed; too many containers
were</span>
<span class="cm"> * failing or some other threshold was reached</span>
<span class="cm"> */</span>
<span class="k">int</span> <span class="no">EXIT_DEPLOYMENT_FAILED</span>
<span class="o">=</span> <span class="mh">73</span><span class="p">;</span>
Modified: websites/staging/slider/trunk/content/docs/manpage.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/manpage.html (original)
+++ websites/staging/slider/trunk/content/docs/manpage.html Wed Oct 15 16:50:03
2014
@@ -489,6 +489,8 @@ YARN application list. Instead it commun
with any applications which has registered itself with the "service
registry"</p>
<p>The <code>--name <name></code> option names the registry entry to
work with. For slider applications,
this is the application instance</p>
+<p>The <code>--user <user></code> option names the user who
owns/deployed the service.
+it defaults to the current user.</p>
<p>The <code>--servicetype <servicetype></code> option allows a
different service type to be chosen.
The default is <code>org-apache-slider</code></p>
<p>The <code>--verbose</code> flag triggers more verbose output on the
operations</p>
@@ -506,9 +508,9 @@ is not found, the command returns the ex
<p>Operations:</p>
<h4
id="slider-registry-list-servicetype-servicetype-name-name-verbose"><code>slider
registry --list [--servicetype <servicetype>] [--name <name>]
[--verbose]</code></h4>
<p>List all services of the service type and optionally the name. </p>
-<h4
id="slider-registry-listconf-name-name-internal-servicetype-servicetype"><code>slider
registry --listconf [--name <name>] [--internal] [--servicetype
<servicetype>]</code></h4>
+<h4
id="slider-registry-listconf-name-name-internal-servicetype-servicetype-user-user"><code>slider
registry --listconf [--name <name>] [--internal] [--servicetype
<servicetype>] [--user <user>]</code></h4>
<p>List the configurations exported by of a named application</p>
-<h4
id="slider-registry-getconf-configuration-format-xmljsonproperties-servicetype-servicetype-name-name-dest-path-internal-get-the-configuration"><code>slider
registry --getconf <configuration> [--format (xml|json|properties)]
[--servicetype <servicetype>] [--name <name>] [--dest <path>]
[--internal]</code> get the configuration</h4>
+<h4
id="slider-registry-getconf-configuration-format-xmljsonproperties-servicetype-servicetype-name-name-dest-path-internal-user-user-get-the-configuration"><code>slider
registry --getconf <configuration> [--format (xml|json|properties)]
[--servicetype <servicetype>] [--name <name>] [--dest <path>]
[--internal] [--user <user>]</code> get the configuration</h4>
<p>Get a named configuration in a chosen format. Default: XML</p>
<p><code>--dest <path></code> : the filename or directory to save a
configuration to.
<code>--format (xml|json|properties)</code> defines the output format</p>
@@ -533,7 +535,7 @@ or lists all service records directly un
<p>The result can be printed to the console (default) or saved to the
filesystem;
the means of specifiying the destination varies depending on whether a single
record or a listing is requested.</p>
-<h3 id="resolve-a-single-entry-slider-resolve-path-path">Resolve a single
entry: <code>slider resolve --path <path></code></h3>
+<h3
id="resolve-a-single-entry-slider-resolve-path-path-out-file-destdir-dir">Resolve
a single entry: <code>slider resolve --path <path> [--out <file>
[--destdir <dir>]</code></h3>
<p>The basic <code>slider resolve --path <path></code> command, without
the <code>--list</code> option
will attempt to resolve the service record at the destination. The record
may be saved to the file specified with the <code>--out</code></p>
@@ -575,6 +577,12 @@ save the results</p>
<p>This will create a directory <code>services</code> and save service records
to it.
If a service <code>"hbase-1"</code> was registered a under this path, its
service record
would be saved to the file <code>services/hbase-1.json</code>.</p>
+<p>The current users base path can be referred to via the "~" prefix:</p>
+<div class="codehilite"><pre><span class="n">slider</span> <span
class="n">resolve</span> <span class="o">--</span><span class="n">path</span>
<span class="o">~/</span><span class="n">services</span><span
class="o">/</span> <span class="o">--</span><span class="n">list</span>
+</pre></div>
+
+
+<p>This simplifies path creation, testing a, </p>
<h3 id="start-name-wait-time"><code>start <name> [--wait
time</code>]</h3>
<p>(<strong>start</strong> used to be <strong>thaw</strong> in develop
branch)</p>
<p>Resume a stopped application instance, recreating it from its previously
saved state. This will include a best-effort attempt to create the same number
of nodes as before, though their locations may be different.</p>
