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 Thu, 21 Mar 2013 01:37:16 GMT

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

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

I verified this on a pseudo-distributed cluster in the following way:
* Started up yarn expecting a namenode port of 7654.
* Started up HDFS with default namenode port of 9000.
* Ran a pi job.
* Verified that log aggregation failed because the nodemanager couldn't find the namenode.
* Restarted HDFS with the namenode port 7654.
* Ran another YARN job.
* Verified that the logs from the second job showed up in the UI and that the logs from the
first job didn't.
                
> 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.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