[jira] [Updated] (YARN-2741) 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
[ https://issues.apache.org/jira/browse/YARN-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-2741: -- Attachment: YARN-2741.6.patch Added unit tests > 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, YARN-2741.6.patch > > > PROBLEM: User is getting "No Logs available for Container Container_" > when setting the yarn.nodemanager.log-dirs to any drive letter other than C: > STEPS TO REPRODUCE: > 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 , > /cluster > 6) Click on the application_id > 7) Click on the logs link, you will get "No Logs available for Container > Container_" > 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 (v6.3.4#6332)
[jira] [Updated] (YARN-2741) 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
[
https://issues.apache.org/jira/browse/YARN-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Welch updated YARN-2741:
--
Attachment: YARN-2741.1.patch
It's a known issue that new java.net.URI(String) looses file specifications on
Windows. If you instead use File.toURI() this does not happen. This patch
switches to that approach and is able to successfully serve up log files with a
configuration like this
{code}
yarn.nodemanager.log-dirs
F:/nmlogs
{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_"
> when setting the yarn.nodemanager.log-dirs to any drive letter other than C:
> STEPS TO REPRODUCE:
> 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 ,
> /cluster
> 6) Click on the application_id
> 7) Click on the logs link, you will get "No Logs available for Container
> Container_"
> 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
(v6.3.4#6332)
[jira] [Updated] (YARN-2741) 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
[ https://issues.apache.org/jira/browse/YARN-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-2741: -- Component/s: nodemanager Environment: Windows Affects Version/s: 2.6.0 Assignee: Craig Welch > 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 > > PROBLEM: User is getting "No Logs available for Container Container_" > when setting the yarn.nodemanager.log-dirs to any drive letter other than C: > STEPS TO REPRODUCE: > 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 , > /cluster > 6) Click on the application_id > 7) Click on the logs link, you will get "No Logs available for Container > Container_" > 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 (v6.3.4#6332)
