Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-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 24998D42C for ; Tue, 13 Nov 2012 03:57:12 +0000 (UTC) Received: (qmail 41296 invoked by uid 500); 13 Nov 2012 03:57:12 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 41104 invoked by uid 500); 13 Nov 2012 03:57:12 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 40972 invoked by uid 99); 13 Nov 2012 03:57:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Nov 2012 03:57:12 +0000 Date: Tue, 13 Nov 2012 03:57:12 +0000 (UTC) From: "Nathan Roberts (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: <1315884842.105276.1352779032301.JavaMail.jiratomcat@arcas> In-Reply-To: <1369256367.102706.1352753232470.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (YARN-212) NM state machine ignores an APPLICATION_CONTAINER_FINISHED event when it shouldn't 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/YARN-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Roberts updated YARN-212: -------------------------------- Attachment: yarn-212.txt Fixed timing issue in TestLogAggregationService > NM state machine ignores an APPLICATION_CONTAINER_FINISHED event when it shouldn't > ---------------------------------------------------------------------------------- > > Key: YARN-212 > URL: https://issues.apache.org/jira/browse/YARN-212 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Affects Versions: 0.23.4, 2.0.1-alpha > Reporter: Nathan Roberts > Assignee: Nathan Roberts > Priority: Blocker > Attachments: yarn-212.txt, yarn-212.txt > > > The NM state machines can make the following two invalid state transitions when a speculative attempt is killed shortly after it gets started. When this happens the NM keeps the log aggregation context open for this application and therefore chews up FDs and leases on the NN, eventually running the NN out of FDs and bringing down the entire cluster. > 2012-11-07 05:36:33,774 [AsyncDispatcher event handler] WARN org.apache.hadoop.yarn.server.nodemanager.containermanager.application.Application: Can't handle this event at current state > org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: APPLICATION_CONTAINER_FINISHED at INITING > 2012-11-07 05:36:33,775 [AsyncDispatcher event handler] WARN org.apache.hadoop.yarn.server.nodemanager.containermanager.container.Container: Can't handle this event at current state: Current: [DONE], eventType: [INIT_CONTAINER] > org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: INIT_CONTAINER at DONE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira