[
https://issues.apache.org/jira/browse/MAPREDUCE-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534900#comment-14534900
]
Hudson commented on MAPREDUCE-6279:
-----------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #2137 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2137/])
MAPREDUCE-6279. AM should explicity exit JVM after all services have stopped.
Contributed by Eric Payne (jlowe: rev f30065c8b6099372f57015b505434120fe83c2b0)
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* hadoop-mapreduce-project/CHANGES.txt
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestMRAppMaster.java
> 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
> Fix For: 2.8.0
>
> Attachments: MAPREDUCE-6279.v1.txt, MAPREDUCE-6279.v2.txt,
> MAPREDUCE-6279.v3.patch, MAPREDUCE-6279.v4.patch
>
>
> 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)
