Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 6 Jun 2013 01:47:21 +0000 (UTC)
From: "Sandy Ryza (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12644965.1367020576995.75742.1370483241002@arcas>
In-Reply-To: <JIRA.12644965.1367020576995@arcas>
References: <JIRA.12644965.1367020576995@arcas>
Subject: [jira] [Commented] (MAPREDUCE-5185) When log aggregation not
 enabled, message should point to NM HTTP port, not IPC port
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sandy Ryza commented on MAPREDUCE-5185:
---------------------------------------

Thanks for looking into this, Niranjan. The message I'm referring to is in the RM web UI, not the logs. Are you able to getThe the message there?

The solution you posted, however, is definitely along the lines that I was thinking.  If possible, it would be nice to augment it to point not to just the NM UI, but to the actual page with the container logs in it.
                
> When log aggregation not enabled, message should point to NM HTTP port, not IPC port 
> -------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5185
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5185
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver
>    Affects Versions: 2.0.4-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>
> When I try to get a container's logs in the JHS without log aggregation enabled, I get a message that looks like this:
> "Aggregation is not enabled. Try the nodemanager at sandy-ThinkPad-T530:33224"
> This could be a lot more helpful by actually pointing the URL that would show the container logs on the NM.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira