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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2012/10/22 21:10:14 UTC

[jira] [Updated] (YARN-174) TestNodeStatusUpdater is failing in trunk

     [ https://issues.apache.org/jira/browse/YARN-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated YARN-174:
-----------------------------------------

    Summary: TestNodeStatusUpdater is failing in trunk  (was: TestNodeStatusUpdate is failing in trunk)
    
> 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
>         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