hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Date Tue, 15 May 2012 23:49:09 GMT

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

Alejandro Abdelnur commented on HADOOP-8393:
--------------------------------------------

+1 lgtm
                
> hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException
MRAppMaster
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8393
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8393
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>         Attachments: HADOOP-8393.patch
>
>
> If you start a pseudo distributed yarn using "start-yarn.sh" you need to specify exports
for HADOOP_COMMON_HOME, HADOOP_HDFS_HOME, YARN_HOME, YARN_CONF_DIR, and HADOOP_MAPRED_HOME
in hadoop-env.sh (or elsewhere), otherwise the spawned node manager will be missing these
in it's environment. This is due to start-yarn using yarn-daemons. With this fix it's possible
to start yarn (etc...) with only HADOOP_CONF_DIR specified in the environment. Took some time
to track down this failure, so seems worthwhile to fix.

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

        

Mime
View raw message