Author: smohanty
Date: Thu Oct 9 01:35:32 2014
New Revision: 1630266
URL: http://svn.apache.org/r1630266
Log:
Doc update for latest develop branch and some corrections
Modified:
incubator/slider/site/trunk/content/docs/getting_started.md
incubator/slider/site/trunk/content/docs/manpage.md
incubator/slider/site/trunk/content/docs/slider_specs/resource_specification.md
Modified: incubator/slider/site/trunk/content/docs/getting_started.md
URL:
http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/docs/getting_started.md?rev=1630266&r1=1630265&r2=1630266&view=diff
==============================================================================
--- incubator/slider/site/trunk/content/docs/getting_started.md (original)
+++ incubator/slider/site/trunk/content/docs/getting_started.md Thu Oct 9
01:35:32 2014
@@ -58,11 +58,12 @@ The Slider deployment has the following
## <a name="setup"></a>Setup the Cluster
-Setting up your Hadoop cluster with the services listed above.
+Set up your Hadoop cluster with the services listed above.
-If you are using a one-box or a sandbox then you may need to modify your YARN
-configuration to allow for multiple, modify your YARN configuration to allow
for multiple
-containers on a single host. In `yarn-site.xml` make the following
modifications:
+*Note:* Ensure the debug delay config is set to a non-zero value to allow easy
debugging.
+If you are using a single VM or a sandbox then you may need to modify your
YARN
+configuration to allow for multiple containers on a single host.
+In `yarn-site.xml` make the following modifications:
<table>
<tr>
Modified: incubator/slider/site/trunk/content/docs/manpage.md
URL:
http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/docs/manpage.md?rev=1630266&r1=1630265&r2=1630266&view=diff
==============================================================================
--- incubator/slider/site/trunk/content/docs/manpage.md (original)
+++ incubator/slider/site/trunk/content/docs/manpage.md Thu Oct 9 01:35:32 2014
@@ -124,8 +124,7 @@ Build and run an application instance of
The `--wait` parameter, if provided, specifies the time to wait until the YARN
application is actually running. Even after the YARN application has started,
there may be some delay for the instance to start up.
-### Arguments for `build` and `create`
-
+#### **Arguments for `build` and `create`**
##### `--package <uri-to-package>`
Modified:
incubator/slider/site/trunk/content/docs/slider_specs/resource_specification.md
URL:
http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/docs/slider_specs/resource_specification.md?rev=1630266&r1=1630265&r2=1630266&view=diff
==============================================================================
---
incubator/slider/site/trunk/content/docs/slider_specs/resource_specification.md
(original)
+++
incubator/slider/site/trunk/content/docs/slider_specs/resource_specification.md
Thu Oct 9 01:35:32 2014
@@ -184,51 +184,7 @@ YARN cluster and hardware.
## <a name="labels"></a>Using Labels
The resources.json file can be used to specify the labels to be used when
allocating containers for the components. The details of the YARN Label feature
can be found at [YARN-796](https://issues.apache.org/jira/browse/YARN-796).
-In summary:
-* Nodes can be assigned one or more labels
-* Capacity Queues can be defined with access to one or more labels
-* Ensure application components are associated with appropriate label
expressions
-* Create the application using specific queue
+The feature is not yet committed.
-This way, you can guarantee that a certain set of nodes are reserved for an
application or for a component within an application.
-
-Label expression is specified through property "yarn.label.expression". When
no label expression is specified then it is assumed that only non-labeled nodes
are used when allocating containers for component instances.
-
-If label expression is specified for slider-appmaster then it also becomes the
default label expression for all component. To take advantage of default label
expression leave out the property (see HBASE_REGIONSERVER in the example).
Label expression with empty string ("yarn.label.expression":"") means nodes
without labels.
-
-### Example
-
-Here is a `resource.json` file for an HBase cluster which uses labels. The
label for the application instance is "hbase1" and the label expression for the
HBASE_MASTER components is "hbase1_master". HBASE_REGIONSERVER instances will
automatically use label "hbase1". Alternatively, if you specify
("yarn.label.expression":"") for HBASE_REGIONSERVER then the containers will
only be allocated on nodes with no labels.
-
- {
- "schema": "http://example.org/specification/v2.0.0";,
- "metadata": {
- },
- "global": {
- },
- "components": {
- "HBASE_MASTER": {
- "yarn.role.priority": "1",
- "yarn.component.instances": "1",
- "yarn.label.expression":"hbase1_master"
- },
- "HBASE_REGIONSERVER": {
- "yarn.role.priority": "1",
- "yarn.component.instances": "1",
- },
- "slider-appmaster": {
- "yarn.label.expression":"hbase1"
- }
- }
- }
-
-Specifically, for the above example you will need:
-* Create two labels, `hbase1` and `hbase1_master` (use yarn rmadmin commands)
-* Assign the labels to nodes (use yarn rmadmin commands)
-* Perform refresh queue (yarn -refreshqueue)
-* Create a queue by defining it in the capacity scheduler config
-* Allow the queue to access to the labels and ensure that appropriate min/max
capacity is assigned
-* Perform refresh queue (yarn -refreshqueue)
-* Create the Slider application against the above queue using parameter
`--queue` while creating the application
-
-## <a name="logagg"></a>Using Log Aggregation
\ No newline at end of file
+## <a name="logagg"></a>Using Log Aggregation
+The feature is not yet committed.
