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 6545395F5 for ; Fri, 1 Jun 2012 22:03:23 +0000 (UTC) Received: (qmail 93128 invoked by uid 500); 1 Jun 2012 22:03:23 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 93058 invoked by uid 500); 1 Jun 2012 22:03:23 -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 93040 invoked by uid 99); 1 Jun 2012 22:03:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2012 22:03:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 0DBD114285F for ; Fri, 1 Jun 2012 22:03:23 +0000 (UTC) Date: Fri, 1 Jun 2012 22:03:23 +0000 (UTC) From: "Robert Joseph Evans (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1520250068.28582.1338588203058.JavaMail.jiratomcat@issues-vm> In-Reply-To: <263568855.27267.1338569363291.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Updated] (MAPREDUCE-4302) NM goes down if error encountered during log aggregation 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-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated MAPREDUCE-4302: ------------------------------------------- Resolution: Fixed Fix Version/s: 3.0.0 2.0.1-alpha 0.23.3 Status: Resolved (was: Patch Available) Thanks Daryn, I put this into trunk, branch-2, and branch-0.23. > NM goes down if error encountered during log aggregation > -------------------------------------------------------- > > Key: MAPREDUCE-4302 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4302 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: nodemanager > Affects Versions: 0.23.0, 2.0.0-alpha, trunk > Reporter: Daryn Sharp > Assignee: Daryn Sharp > Priority: Critical > Fix For: 0.23.3, 2.0.1-alpha, 3.0.0 > > Attachments: MAPREDUCE-4302.patch > > > When a container launch request is sent to the NM, if _any_ exception occurs during the init of log aggregation then the NM goes down. The problem can be induced by situations including, but certainly not limited to: transient rpc connection issues, missing tokens, expired tokens, permissions, full/quota exceeded dfs, etc. The problem may occur with and without security enabled. > The ramification is an entire cluster can be rather easily brought down either maliciously, accidentally, or via a submission bug. -- 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