hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6279) AM should explicity exit JVM after all services have stopped
Date Thu, 07 May 2015 22:08:00 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Lowe updated MAPREDUCE-6279:
----------------------------------
    Labels:   (was: BB2015-05-TBR)

> 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, 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)

Mime
View raw message