[
https://issues.apache.org/jira/browse/MAPREDUCE-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384871#comment-14384871
]
Hadoop QA commented on MAPREDUCE-6279:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12707896/MAPREDUCE-6279.v1.txt
against trunk revision 3836ad6.
{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}. There were no new javadoc 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 2.0.3) 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-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app:
org.apache.hadoop.mapreduce.jobhistory.TestJobHistoryEventHandler
The following test timeouts occurred in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app:
org.apache.hadoop.mapreduce.v2.app.TestStagingCleanup
org.apache.hadoop.mapreduce.v2.app.TestJobEndNotifier
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5345//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5345//console
This message is automatically generated.
> AM should explicity exit JVM after all services have stopped
> ------------------------------------------------------------
>
> Key: MAPREDUCE-6279
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6279
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 2.5.0
> Reporter: Jason Lowe
> Assignee: Eric Payne
> Attachments: MAPREDUCE-6279.v1.txt
>
>
> Occasionally the MapReduce AM can "get stuck" trying to shut down.
> MAPREDUCE-6049 and MAPREDUCE-5888 were specific instances that have been
> fixed, but this can also occur with uber jobs if the task code inadvertently
> leaves non-daemon threads lingering.
> We should explicitly shutdown the JVM after the MapReduce AM has unregistered
> and all services have been stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
