[
https://issues.apache.org/jira/browse/YARN-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482336#comment-13482336
]
Hudson commented on YARN-174:
-----------------------------
Integrated in Hadoop-Mapreduce-trunk #1234 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1234/])
YARN-174. Modify NodeManager to pass the user's configuration even when
rebooting. Contributed by Vinod Kumar Vavilapalli. (Revision 1401086)
Result = SUCCESS
vinodkv :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1401086
Files :
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeManager.java
> TestNodeStatusUpdater is failing in trunk
> -----------------------------------------
>
> Key: YARN-174
> URL: https://issues.apache.org/jira/browse/YARN-174
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.0.0
> Reporter: Robert Joseph Evans
> Assignee: Vinod Kumar Vavilapalli
> Fix For: 2.0.2-alpha, 0.23.5
>
> Attachments: YARN-174-20121022.txt, YARN-174.patch
>
>
> {noformat}
> 2012-10-19 12:18:23,941 FATAL [Node Status Updater] nodemanager.NodeManager
> (NodeManager.java:initAndStartNodeManager(277)) - Error starting NodeManager
> org.apache.hadoop.yarn.YarnException: ${yarn.log.dir}/userlogs is not a valid
> path. Path should be with file scheme or without scheme
> at
> org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService.validatePaths(LocalDirsHandlerService.java:321)
> at
> org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService$MonitoringTimerTask.<init>(LocalDirsHandlerService.java:95)
> at
> org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService.init(LocalDirsHandlerService.java:123)
> at
> org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeHealthCheckerService.init(NodeHealthCheckerService.java:48)
> at
> org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.init(NodeManager.java:165)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:274)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeManager.stateChanged(NodeManager.java:256)
> at
> org.apache.hadoop.yarn.service.AbstractService.changeState(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.service.AbstractService.stop(AbstractService.java:112)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.stop(NodeStatusUpdaterImpl.java:149)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.reboot(NodeStatusUpdaterImpl.java:157)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.access$900(NodeStatusUpdaterImpl.java:63)
> at
> org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl$1.run(NodeStatusUpdaterImpl.java:357)
> {noformat}
> The NM then calls System.exit(-1), which makes the unit test exit and
> produces an error that is hard to track down.
--
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
