[ https://issues.apache.org/jira/browse/MAPREDUCE-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne updated MAPREDUCE-6279: ---------------------------------- Attachment: (was: MAPREDUCE-6279.v2.txt) > 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)