hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-24) Nodemanager fails to start if log aggregation enabled and namenode unavailable
Date Tue, 26 Mar 2013 19:59:15 GMT

    [ https://issues.apache.org/jira/browse/YARN-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614486#comment-13614486
] 

Sandy Ryza commented on YARN-24:
--------------------------------

Thinking about this a little more, I didn't see a strong reason not to verify the root log
dir each time.  This makes the log aggregation service resilient to the root directory being
deleted or chmoded while a nodemanager is running.  Uploaded a new patch that does this.
                
> 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-2.patch, YARN-24-3.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

Mime
View raw message