[
https://issues.apache.org/jira/browse/BIGTOP-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227614#comment-13227614
]
Roman Shaposhnik commented on BIGTOP-445:
-----------------------------------------
I just looked at the latest artifacts for CentOS 5 and the correct files
appears to reside in the corresponding package:
http://bigtop01.cloudera.org:8080/view/Bigtop-hadoop-0.23/job/Bigtop-hadoop-0.23-Hadoop/label=centos5/18/artifact/output/hadoop/hadoop-yarn-resourcemanager-0.23.3.18-1.x86_64.rpm
Please let me know if you happen to see this problem on any particular platform.
> yarn default file has the wrong name
> ------------------------------------
>
> Key: BIGTOP-445
> URL: https://issues.apache.org/jira/browse/BIGTOP-445
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Bruno Mahé
> Assignee: Roman Shaposhnik
>
> In yarn resource/node manager init script you can see:
> {noformat}
> if [ -f /etc/default/hadoop-yarn-resourcemanager ] ; then
> . /etc/default/hadoop-yarn-resourcemanager
> fi
> {noformat}
> Unfortunately, only the following file exist:
> {noformat}
> /etc/default/yarn
> {noformat}
> So the RM/NM fail to start since it cannot source the default file and
> therefore missing some very important env variables
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
