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-174) TestNodeStatusUpdate is failing in trunk
Date Fri, 19 Oct 2012 17:56:12 GMT

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

Sandy Ryza commented on YARN-174:
---------------------------------

Aaah, I was running into this when testing for YARN-170 and thought it was a problem with
my code.
                
> TestNodeStatusUpdate 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
>
> {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

Mime
View raw message