Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D0047D2C4 for ; Tue, 17 Jul 2012 15:13:36 +0000 (UTC) Received: (qmail 40566 invoked by uid 500); 17 Jul 2012 15:13:36 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 40407 invoked by uid 500); 17 Jul 2012 15:13:35 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 40373 invoked by uid 99); 17 Jul 2012 15:13:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jul 2012 15:13:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 101D9140541 for ; Tue, 17 Jul 2012 15:13:35 +0000 (UTC) Date: Tue, 17 Jul 2012 15:13:35 +0000 (UTC) From: "Daryn Sharp (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <512823290.64269.1342538015068.JavaMail.jiratomcat@issues-vm> In-Reply-To: <321246811.59793.1342465955426.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (MAPREDUCE-4448) Nodemanager crashes upon application cleanup if aggregation failed to start MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416277#comment-13416277 ] Daryn Sharp commented on MAPREDUCE-4448: ---------------------------------------- Just noticed there's a race condition that can cause a NPE. There is a {{containsKey(appid}} followed by {{get(appid}}. If the aggregator fails and removes itself from the map between those two calls, the NM goes down again. > Nodemanager crashes upon application cleanup if aggregation failed to start > --------------------------------------------------------------------------- > > Key: MAPREDUCE-4448 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4448 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, nodemanager > Affects Versions: 0.23.3, 2.0.1-alpha > Reporter: Jason Lowe > Assignee: Jason Lowe > Priority: Critical > Attachments: MAPREDUCE-4448.patch > > > When log aggregation is enabled, the nodemanager can crash if log aggregation for an application failed to start. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira