[
https://issues.apache.org/jira/browse/YARN-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438062#comment-13438062
]
Vinod Kumar Vavilapalli commented on YARN-24:
---------------------------------------------
Log aggregation is a criticial service when enabled, and so, yes, it was a
conscious decision to shut-down NM if it can't reach NameNode.
But you are right, NN can go down anytime, so we should handle that case along
with this. We need some way for apps to know that this NM couldn't upload logs
in the past due to a downtime in DFS, have any ideas?
> 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: 2.1.0-alpha, 0.23.3
> Reporter: Jason Lowe
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
