[jira] [Commented] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[
https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610410#comment-13610410
]
Hadoop QA commented on YARN-498:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12575024/YARN-498.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{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-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/570//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/570//console
This message is automatically generated.
> Unmanaged AM launcher does not set various constants in env for an AM, also
> does not handle failed AMs properly
> ---
>
> Key: YARN-498
> URL: https://issues.apache.org/jira/browse/YARN-498
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Hitesh Shah
>Assignee: Hitesh Shah
> Attachments: YARN-498.1.patch, YARN-498.wip.patch
>
>
> Currently, it only sets the app attempt id which is really not required as
> AMs are only expected to extract it from the container id.
--
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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[
https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610645#comment-13610645
]
Hadoop QA commented on YARN-498:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12575029/YARN-498.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 tests included appear to have a timeout.{color}
{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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher:
org.apache.hadoop.yarn.applications.unmanagedamlauncher.TestUnmanagedAMLauncher
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/572//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/572//console
This message is automatically generated.
> Unmanaged AM launcher does not set various constants in env for an AM, also
> does not handle failed AMs properly
> ---
>
> Key: YARN-498
> URL: https://issues.apache.org/jira/browse/YARN-498
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Hitesh Shah
>Assignee: Hitesh Shah
> Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.wip.patch
>
>
> Currently, it only sets the app attempt id which is really not required as
> AMs are only expected to extract it from the container id.
--
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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[ https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610918#comment-13610918 ] Hitesh Shah commented on YARN-498: -- Test failure seems to be due to YARN-417. > Unmanaged AM launcher does not set various constants in env for an AM, also > does not handle failed AMs properly > --- > > Key: YARN-498 > URL: https://issues.apache.org/jira/browse/YARN-498 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.wip.patch > > > Currently, it only sets the app attempt id which is really not required as > AMs are only expected to extract it from the container id. -- 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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[ https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611000#comment-13611000 ] Bikas Saha commented on YARN-498: - I had originally left the loop without a timeout because eventually YARN is supposed to recognize that the app succeeded/killed/failed or it would expire and fail the app. Is that not happening? I agree that a timeout would be more useful. How about adding a timeout to the monitoring method such that it throws an exception if the desired end state is not reached within that time. With the code change in the patch, it would end up crashing with an NPE, right? > Unmanaged AM launcher does not set various constants in env for an AM, also > does not handle failed AMs properly > --- > > Key: YARN-498 > URL: https://issues.apache.org/jira/browse/YARN-498 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.wip.patch > > > Currently, it only sets the app attempt id which is really not required as > AMs are only expected to extract it from the container id. -- 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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[
https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611071#comment-13611071
]
Hadoop QA commented on YARN-498:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12575066/YARN-498.3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 tests included appear to have a timeout.{color}
{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:red}-1 eclipse:eclipse{color}. The patch failed to build 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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher:
org.apache.hadoop.yarn.applications.unmanagedamlauncher.TestUnmanagedAMLauncher
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/574//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/574//console
This message is automatically generated.
> Unmanaged AM launcher does not set various constants in env for an AM, also
> does not handle failed AMs properly
> ---
>
> Key: YARN-498
> URL: https://issues.apache.org/jira/browse/YARN-498
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Hitesh Shah
>Assignee: Hitesh Shah
> Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.3.patch,
> YARN-498.wip.patch
>
>
> Currently, it only sets the app attempt id which is really not required as
> AMs are only expected to extract it from the container id.
--
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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[ https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612923#comment-13612923 ] Bikas Saha commented on YARN-498: - Looks good. Thanks for the changes. +1. Some minor nits 1) Might be good to do currentTime - startTime > 5 seconds instead of using a counter. That way its delinked from the the sleep period of the loop. 2) Can we include the expected and actual states in the final exception. It would be convenient to see what state the app was in when we expected it to reach some other state. 3) The new test might have to change because YARN-417 changed DistShell to not accept 0 container launches. So the test will get an exception but not the one it expects. Maybe add check that exception contains expected message? > Unmanaged AM launcher does not set various constants in env for an AM, also > does not handle failed AMs properly > --- > > Key: YARN-498 > URL: https://issues.apache.org/jira/browse/YARN-498 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.3.patch, > YARN-498.wip.patch > > > Currently, it only sets the app attempt id which is really not required as > AMs are only expected to extract it from the container id. -- 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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[
https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613010#comment-13613010
]
Hadoop QA commented on YARN-498:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12575368/YARN-498.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{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-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/586//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/586//console
This message is automatically generated.
> Unmanaged AM launcher does not set various constants in env for an AM, also
> does not handle failed AMs properly
> ---
>
> Key: YARN-498
> URL: https://issues.apache.org/jira/browse/YARN-498
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Hitesh Shah
>Assignee: Hitesh Shah
> Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.3.patch,
> YARN-498.4.patch, YARN-498.wip.patch
>
>
> Currently, it only sets the app attempt id which is really not required as
> AMs are only expected to extract it from the container id.
--
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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[ https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613410#comment-13613410 ] Bikas Saha commented on YARN-498: - Looks good. +1. > Unmanaged AM launcher does not set various constants in env for an AM, also > does not handle failed AMs properly > --- > > Key: YARN-498 > URL: https://issues.apache.org/jira/browse/YARN-498 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.3.patch, > YARN-498.4.patch, YARN-498.wip.patch > > > Currently, it only sets the app attempt id which is really not required as > AMs are only expected to extract it from the container id. -- 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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[ https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613420#comment-13613420 ] Bikas Saha commented on YARN-498: - Committed to trunk and branch-2 > Unmanaged AM launcher does not set various constants in env for an AM, also > does not handle failed AMs properly > --- > > Key: YARN-498 > URL: https://issues.apache.org/jira/browse/YARN-498 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.3.patch, > YARN-498.4.patch, YARN-498.wip.patch > > > Currently, it only sets the app attempt id which is really not required as > AMs are only expected to extract it from the container id. -- 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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[ https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613423#comment-13613423 ] Hudson commented on YARN-498: - Integrated in Hadoop-trunk-Commit #3527 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3527/]) YARN-498. Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly (Hitesh Shah via bikas) (Revision 1460954) Result = SUCCESS bikas : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1460954 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/main/java/org/apache/hadoop/yarn/applications/distributedshell/ApplicationMaster.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/main/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/UnmanagedAMLauncher.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/test/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/TestUnmanagedAMLauncher.java > Unmanaged AM launcher does not set various constants in env for an AM, also > does not handle failed AMs properly > --- > > Key: YARN-498 > URL: https://issues.apache.org/jira/browse/YARN-498 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.3.patch, > YARN-498.4.patch, YARN-498.wip.patch > > > Currently, it only sets the app attempt id which is really not required as > AMs are only expected to extract it from the container id. -- 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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[ https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613679#comment-13613679 ] Hudson commented on YARN-498: - Integrated in Hadoop-Yarn-trunk #167 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/167/]) YARN-498. Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly (Hitesh Shah via bikas) (Revision 1460954) Result = SUCCESS bikas : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1460954 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/main/java/org/apache/hadoop/yarn/applications/distributedshell/ApplicationMaster.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/main/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/UnmanagedAMLauncher.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/test/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/TestUnmanagedAMLauncher.java > Unmanaged AM launcher does not set various constants in env for an AM, also > does not handle failed AMs properly > --- > > Key: YARN-498 > URL: https://issues.apache.org/jira/browse/YARN-498 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.3.patch, > YARN-498.4.patch, YARN-498.wip.patch > > > Currently, it only sets the app attempt id which is really not required as > AMs are only expected to extract it from the container id. -- 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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[ https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613752#comment-13613752 ] Hudson commented on YARN-498: - Integrated in Hadoop-Hdfs-trunk #1356 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1356/]) YARN-498. Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly (Hitesh Shah via bikas) (Revision 1460954) Result = FAILURE bikas : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1460954 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/main/java/org/apache/hadoop/yarn/applications/distributedshell/ApplicationMaster.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/main/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/UnmanagedAMLauncher.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/test/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/TestUnmanagedAMLauncher.java > Unmanaged AM launcher does not set various constants in env for an AM, also > does not handle failed AMs properly > --- > > Key: YARN-498 > URL: https://issues.apache.org/jira/browse/YARN-498 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.3.patch, > YARN-498.4.patch, YARN-498.wip.patch > > > Currently, it only sets the app attempt id which is really not required as > AMs are only expected to extract it from the container id. -- 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] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
[ https://issues.apache.org/jira/browse/YARN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614018#comment-13614018 ] Hudson commented on YARN-498: - Integrated in Hadoop-Mapreduce-trunk #1384 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1384/]) YARN-498. Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly (Hitesh Shah via bikas) (Revision 1460954) Result = FAILURE bikas : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1460954 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/main/java/org/apache/hadoop/yarn/applications/distributedshell/ApplicationMaster.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/main/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/UnmanagedAMLauncher.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher/src/test/java/org/apache/hadoop/yarn/applications/unmanagedamlauncher/TestUnmanagedAMLauncher.java > Unmanaged AM launcher does not set various constants in env for an AM, also > does not handle failed AMs properly > --- > > Key: YARN-498 > URL: https://issues.apache.org/jira/browse/YARN-498 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.3.patch, > YARN-498.4.patch, YARN-498.wip.patch > > > Currently, it only sets the app attempt id which is really not required as > AMs are only expected to extract it from the container id. -- 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
