You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Eric Payne (JIRA)" <ji...@apache.org> on 2015/03/18 19:09:40 UTC
[jira] [Assigned] (MAPREDUCE-6279) AM should explicity exit JVM
after all services have stopped
[ https://issues.apache.org/jira/browse/MAPREDUCE-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne reassigned MAPREDUCE-6279:
-------------------------------------
Assignee: Eric Payne
> 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
>
> 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)