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 "Jason Lowe (JIRA)" <ji...@apache.org> on 2015/03/18 19:09:38 UTC
[jira] [Created] (MAPREDUCE-6279) AM should explicity exit JVM
after all services have stopped
Jason Lowe created MAPREDUCE-6279:
-------------------------------------
Summary: 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
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)