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/09/27 17:34:08 UTC
[jira] [Commented] (YARN-22) Using URI for yarn.nodemanager log
dirs fails
[ https://issues.apache.org/jira/browse/YARN-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464819#comment-13464819 ]
Jason Lowe commented on YARN-22:
--------------------------------
Note that using a URI for the nodemanager local/log dirs isn't really fixed. While using a URI no longe crashes the rendering of the web pages, the directories themselves aren't really created as intended. As Sidd mentioned in [this comment|https://issues.apache.org/jira/browse/YARN-22?focusedCommentId=13432267&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13432267] the test is using an absolute path that most users will not be able to create properly when the test runs. Yet the test passes because it's not doing what the user intended. The log directory of file:///target/TestNMWebServerLogDir ends up being transformed by the LocalDirsHandlerService into ./file:/target/TestNMWebServerLogDir rather than /target/TestNMWebServerLogDir.
> Using URI for yarn.nodemanager log dirs fails
> ---------------------------------------------
>
> Key: YARN-22
> URL: https://issues.apache.org/jira/browse/YARN-22
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 0.23.3
> Reporter: Eli Collins
> Assignee: Mayank Bansal
> Priority: Minor
> Fix For: 2.0.2-alpha
>
> Attachments: MAPREDUCE-4466-trunk-v1.patch, MAPREDUCE-4466-trunk-v2.patch, MAPREDUCE-4466-trunk-v3.patch, MAPREDUCE-4466-trunk-v4.patch, YARN-22-trunk-v5.patch
>
>
> If I use URIs (eg file:///home/eli/hadoop/dirs) for yarn.nodemanager.log-dirs or yarn.nodemanager.remote-app-log-dir the container log servlet fails with an NPE (works if I remove the "file" scheme). Using a URI for yarn.nodemanager.local-dirs works.
--
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