Varun Vasudev commented on YARN-2741:

[~cwelch] we should add some sort of unit test to confirm the behavior. I can 
see this bug getting re-introduced by mistake if someone is adding 
functionality or re-factoring code.

> Windows: Node manager cannot serve up log files via the web user interface 
> when yarn.nodemanager.log-dirs to any drive letter other than C: (or, the 
> drive that nodemanager is running on)
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>                 Key: YARN-2741
>                 URL: https://issues.apache.org/jira/browse/YARN-2741
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.6.0
>         Environment: Windows
>            Reporter: Craig Welch
>            Assignee: Craig Welch
>         Attachments: YARN-2741.1.patch
> PROBLEM: User is getting "No Logs available for Container Container_<number>" 
> when setting the yarn.nodemanager.log-dirs to any drive letter other than C:
> On Windows
> 1) Run NodeManager on C:
> 2) Create two local drive partitions D: and E:
> 3) Put yarn.nodemanager.log-dirs = D:\nmlogs or E:\nmlogs
> 4) Run a MR job that will last at least 5 minutes
> 5) While the job is in flight, log into the Yarn web ui , 
> <resource_manager_server:8088>/cluster
> 6) Click on the application_id<number>
> 7) Click on the logs link, you will get "No Logs available for Container 
> Container_<number>"
> ACTUAL BEHAVIOR: Getting an error message when viewing the container logs
> EXPECTED BEHAVIOR: Able to use different drive letters in 
> yarn.nodemanager.log-dirs and not get error
> NOTE: If we use the drive letter C: in yarn.nodemanager.log-dirs, we are able 
> to see the container logs while the MR job is in flight.

This message was sent by Atlassian JIRA

Reply via email to