[ 
https://issues.apache.org/jira/browse/HADOOP-10050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797411#comment-13797411
 ] 

Hitesh Shah commented on HADOOP-10050:
--------------------------------------

Comments: 

The capacity-scheduler configs are removed from SingleCluster.apt.vm - any 
reason for this?  
Generated SingleCluster.html has "Set $$YARN_CONF_DIR" - mind fixing this too?

{code}
Run ResourceManager and NodeManager as:

$ cd $HADOOP_MAPRED_HOME
$ sbin/yarn-daemon.sh start resourcemanager
$ sbin/yarn-daemon.sh start nodemanager
$ sbin/mr-jobhistory-daemon.sh start historyserver
{code}

yarn-daemon.sh is not meant to be in HADOOP_MAPRED_HOME. 

If this doc needs to be fixed, there are probably a lot of confusing references 
to HADOOP_PREFIX vs HADOOP_YARN_HOME etc which probably need to be ironed out. 
It may be good to either address them in this jira or file a new one for a 
follow-up. 

> 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)

Reply via email to