Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 18 Mar 2015 18:09:38 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12782968.1426702124000.133899.1426702178942@Atlassian.JIRA>
In-Reply-To: <JIRA.12782968.1426702124000@Atlassian.JIRA>
References: <JIRA.12782968.1426702124000@Atlassian.JIRA>
 <JIRA.12782968.1426702124455@arcas>
Subject: [jira] [Created] (MAPREDUCE-6279) AM should explicity exit JVM
 after all services have stopped
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)