[
https://issues.apache.org/jira/browse/MAPREDUCE-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated MAPREDUCE-4466:
--------------------------------------
Fix Version/s: (was: trunk)
Target Version/s: 2.2.0-alpha
Affects Version/s: 0.23.3
Status: Open (was: Patch Available)
Looks like actual log rendering will also be broken - further up in
ContainerLogsPage {{new File(this.dirsHandler.getLogPathToRead(}}. Also,
changing {{getContainerLogDirs}} may be a cleaner fix.
If testNMWebServer.testNMWebApp is modified to use "file://" - it ends up
creating a dir structure with "file://" being the top level directory under the
current working dir. That could be modified to verify the patch.
All access to the local-dirs and log-dirs happens via the
LocalDirsHandlerService - maybe we should have this convert URIs to simple
strings. file:// works in other places - since {{Path}} is used instead of
{{File}}.
> Using URI for yarn.nodemanager log dirs fails
> ---------------------------------------------
>
> Key: MAPREDUCE-4466
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4466
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.23.3
> Reporter: Eli Collins
> Assignee: Mayank Bansal
> Priority: Minor
> Attachments: MAPREDUCE-4466-trunk-v1.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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
