You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2012/08/15 23:01:40 UTC
[jira] [Commented] (YARN-24) Nodemanager fails to start if log
aggregation enabled and namenode unavailable
[ https://issues.apache.org/jira/browse/YARN-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435522#comment-13435522 ]
Jason Lowe commented on YARN-24:
--------------------------------
Exception on startup is the following, which leads to a general shutdown of the nodemanager
{noformat}
2012-08-15 20:56:33,506 ERROR service.CompositeService (CompositeService.java:start(72)) - Error starting services org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl
org.apache.hadoop.yarn.YarnException: Failed to check for existence of remoteLogDir [/tmp/logs]
at org.apache.hadoop.yarn.server.nodemanager.containermanager.logaggregation.LogAggregationService.verifyAndCreateRemoteLogDir(LogAggregationService.java:159)
at org.apache.hadoop.yarn.server.nodemanager.containermanager.logaggregation.LogAggregationService.start(LogAggregationService.java:134)
at org.apache.hadoop.yarn.service.CompositeService.start(CompositeService.java:68)
at org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.start(ContainerManagerImpl.java:251)
at org.apache.hadoop.yarn.service.CompositeService.start(CompositeService.java:68)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.start(NodeManager.java:178)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:270)
at org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:286)
{noformat}
The nodemanager doesn't immediately fallover if the RM is unavailable, so it seems like we shouldn't if the NN is unavailable. Maybe lazy intialization of the app log directory rather than forcing it to be there on startup?
> 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