Return-Path: 
 <yarn-issues-return-39508-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id E5D7D178F7
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Tue, 28 Oct 2014 07:07:34 +0000 (UTC)
Received: (qmail 84057 invoked by uid 500); 28 Oct 2014 07:07:34 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 84014 invoked by uid 500); 28 Oct 2014 07:07:34 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 84001 invoked by uid 99); 28 Oct 2014 07:07:34 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2014 07:07:34 +0000
Date: Tue, 28 Oct 2014 07:07:34 +0000 (UTC)
From: "Varun Vasudev (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12750491.1414193426000.351796.1414480054649@Atlassian.JIRA>
In-Reply-To: <JIRA.12750491.1414193426000@Atlassian.JIRA>
References: <JIRA.12750491.1414193426000@Atlassian.JIRA>
 <JIRA.12750491.1414193426259@arcas>
Subject: [jira] [Commented] (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 is running
 on)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/YARN-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186494#comment-14186494 ] 

Varun Vasudev commented on YARN-2741:
-------------------------------------

+1, patch looks good.

> 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_<number>" 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 , <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
(v6.3.4#6332)