Return-Path: 
 <yarn-issues-return-72491-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 D668918B19
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Tue, 27 Oct 2015 10:55:20 +0000 (UTC)
Received: (qmail 42365 invoked by uid 500); 27 Oct 2015 10:48:28 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 42318 invoked by uid 500); 27 Oct 2015 10:48:28 -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 42288 invoked by uid 99); 27 Oct 2015 10:48:27 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2015 10:48:27 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id B775A2C033A
	for <yarn-issues@hadoop.apache.org>; Tue, 27 Oct 2015 10:48:27 +0000 (UTC)
Date: Tue, 27 Oct 2015 10:48:27 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12908186.1445942778000.71039.1445942907746@Atlassian.JIRA>
In-Reply-To: <JIRA.12908186.1445942778000@Atlassian.JIRA>
References: <JIRA.12908186.1445942778000@Atlassian.JIRA>
 <JIRA.12908186.1445942778124@arcas>
Subject: [jira] [Updated] (YARN-4303) Confusing help message if AM logs cant
 be retrieved via yarn logs command
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-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Varun Saxena updated YARN-4303:
-------------------------------
    Description: 
{noformat}
yarn@BLR1000002525:~/test/install/hadoop/resourcemanager/bin> ./yarn logs --applicationId application_1445832014581_0028 -am ALL
Can not get AMContainers logs for the application:application_1445832014581_0028
This application:application_1445832014581_0028 is finished. Please enable the application history service. Or Using yarn logs -applicationId <appId> -containerId <containerId> --nodeAddress <nodeHttpAddress> to get the container logs
{noformat}

The command mentioned above is  {{yarn logs -applicationId <appId> -containerId <containerId> --nodeAddress <nodeHttpAddress>}}. It asks you to specify nodeHttpAddress which makes it sound like we have to connect to Node's http port and may lead user to think that they have to connect to nodemanager's webapp address.

This help message should be changed to include command as {{yarn logs -applicationId <appId> -containerId <containerId> --nodeAddress <Node Address>}}

  was:
{noformat}
yarn@BLR1000002525:~/test/install/hadoop/resourcemanager/bin> ./yarn logs --applicationId application_1445832014581_0028 -am ALL
Can not get AMContainers logs for the application:application_1445832014581_0028
This application:application_1445832014581_0028 is finished. Please enable the application history service. Or Using yarn logs -applicationId <appId> -containerId <containerId> --nodeAddress <nodeHttpAddress> to get the container logs
{noformat}

The command mentioned above is  {{yarn logs -applicationId <appId> -containerId <containerId> --nodeAddress <nodeHttpAddress>}}. It asks you to specify nodeHttpAddress which makes it sound like we have to connect to Node's http port and may lead user to think that they have to connect to nodemanager's webapp address.

This command should be changed to {{yarn logs -applicationId <appId> -containerId <containerId> --nodeAddress <Node Address>}}


> Confusing help message if AM logs cant be retrieved via yarn logs command
> -------------------------------------------------------------------------
>
>                 Key: YARN-4303
>                 URL: https://issues.apache.org/jira/browse/YARN-4303
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>            Priority: Minor
>
> {noformat}
> yarn@BLR1000002525:~/test/install/hadoop/resourcemanager/bin> ./yarn logs --applicationId application_1445832014581_0028 -am ALL
> Can not get AMContainers logs for the application:application_1445832014581_0028
> This application:application_1445832014581_0028 is finished. Please enable the application history service. Or Using yarn logs -applicationId <appId> -containerId <containerId> --nodeAddress <nodeHttpAddress> to get the container logs
> {noformat}
> The command mentioned above is  {{yarn logs -applicationId <appId> -containerId <containerId> --nodeAddress <nodeHttpAddress>}}. It asks you to specify nodeHttpAddress which makes it sound like we have to connect to Node's http port and may lead user to think that they have to connect to nodemanager's webapp address.
> This help message should be changed to include command as {{yarn logs -applicationId <appId> -containerId <containerId> --nodeAddress <Node Address>}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)