[
https://issues.apache.org/jira/browse/HADOOP-10050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796428#comment-13796428
]
Hadoop QA commented on HADOOP-10050:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12608652/HADOOP-10050.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3226//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3226//console
This message is automatically generated.
> Update single node and cluster install instructions to work with latest bits
> ----------------------------------------------------------------------------
>
> Key: HADOOP-10050
> URL: https://issues.apache.org/jira/browse/HADOOP-10050
> Project: Hadoop Common
> Issue Type: Bug
> Components: documentation
> Affects Versions: 2.2.0
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Priority: Minor
> Attachments: ClusterSetup.html, HADOOP-10050.patch, mapred-site.xml,
> SingleCluster.html, yarn-site.xml
>
>
> A few things i noticed
> 1. changes to yarn.nodemanager.aux-services
> 2. Set the framework to yarn in mapred-site.xml
> 3. Start the history server
> Also noticed no change to the capacity scheduler configs was needed.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
