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 2E05BDD74 for ; Mon, 11 Mar 2013 23:45:13 +0000 (UTC) Received: (qmail 30230 invoked by uid 500); 11 Mar 2013 23:45:13 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 30201 invoked by uid 500); 11 Mar 2013 23:45:13 -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 30190 invoked by uid 99); 11 Mar 2013 23:45:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Mar 2013 23:45:13 +0000 Date: Mon, 11 Mar 2013 23:45:13 +0000 (UTC) From: "Alejandro Abdelnur (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-24) Nodemanager fails to start if log aggregation enabled and namenode unavailable 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-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599490#comment-13599490 ] Alejandro Abdelnur commented on YARN-24: ---------------------------------------- The approach looks good. Possible to have a testcase? Have you tests it in a cluster forcing the non-creation of the root log dir? > Nodemanager fails to start if log aggregation enabled and namenode unavailable > ------------------------------------------------------------------------------ > > Key: YARN-24 > URL: https://issues.apache.org/jira/browse/YARN-24 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Affects Versions: 0.23.3, 2.0.0-alpha > Reporter: Jason Lowe > Assignee: Sandy Ryza > Attachments: YARN-24-1.patch, YARN-24.patch > > > If log aggregation is enabled and the namenode is currently unavailable, the nodemanager fails to startup. -- 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