You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2012/05/11 20:54:50 UTC
[jira] [Created] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Patrick Hunt created HADOOP-8393:
------------------------------------
Summary: 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
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
[jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276726#comment-13276726 ]
Hudson commented on HADOOP-8393:
--------------------------------
Integrated in Hadoop-Hdfs-trunk #1045 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1045/])
HADOOP-8393. hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster. (phunt via tucu) (Revision 1338998)
Result = FAILURE
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1338998
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
> 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
> Fix For: 2.0.1
>
> 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
[jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated HADOOP-8393:
---------------------------------
Attachment: HADOOP-8393.patch
Exported the necessary vars. I tested by packaging everything up, starting start-dfs and start-yarn (with a single "localhost" slave) and then running a pi job from examples. Works with the patch, doesn't w/o.
> 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
[jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276446#comment-13276446 ]
Hudson commented on HADOOP-8393:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #2250 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2250/])
HADOOP-8393. hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster. (phunt via tucu) (Revision 1338998)
Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1338998
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
> 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
> Fix For: 2.0.1
>
> 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
[jira] [Updated] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated HADOOP-8393:
---------------------------------
Status: Patch Available (was: Open)
> 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
[jira] [Updated] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Robert Joseph Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans updated HADOOP-8393:
----------------------------------------
Fix Version/s: (was: 2.0.1-alpha)
0.23.3
> 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
> Fix For: 0.23.3
>
> 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
[jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407049#comment-13407049 ]
Hudson commented on HADOOP-8393:
--------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #304 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/304/])
svn merge -c 1338998 FIXES: HADOOP-8393 hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster. (phunt via tucu) (Revision 1356763)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1356763
Files :
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
> 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
> Fix For: 0.23.3
>
> 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
[jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276465#comment-13276465 ]
Hudson commented on HADOOP-8393:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #2267 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2267/])
HADOOP-8393. hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster. (phunt via tucu) (Revision 1338998)
Result = ABORTED
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1338998
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
> 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
> Fix For: 2.0.1
>
> 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
[jira] [Closed] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy closed HADOOP-8393.
---------------------------------
> 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
> Fix For: 0.23.3, 2.0.2-alpha
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Ahmed Radwan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276027#comment-13276027 ]
Ahmed Radwan commented on HADOOP-8393:
--------------------------------------
lgtm +1, thanks Patrick!
> 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
[jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276442#comment-13276442 ]
Hudson commented on HADOOP-8393:
--------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2324 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2324/])
HADOOP-8393. hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster. (phunt via tucu) (Revision 1338998)
Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1338998
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
> 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
> Fix For: 2.0.1
>
> 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
[jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273562#comment-13273562 ]
Hadoop QA commented on HADOOP-8393:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12526559/HADOOP-8393.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in hadoop-common-project/hadoop-common.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/985//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/985//console
This message is automatically generated.
> 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
[jira] [Commented] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276754#comment-13276754 ]
Hudson commented on HADOOP-8393:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk #1081 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1081/])
HADOOP-8393. hadoop-config.sh missing variable exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster. (phunt via tucu) (Revision 1338998)
Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1338998
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
> 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
> Fix For: 2.0.1
>
> 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
[jira] [Updated] (HADOOP-8393) hadoop-config.sh missing variable
exports, causes Yarn jobs to fail with ClassNotFoundException MRAppMaster
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated HADOOP-8393:
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.1
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks Patrick. committed to trunk and branch-2.
> 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
> Fix For: 2.0.1
>
> 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