[
https://issues.apache.org/jira/browse/YARN-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060942#comment-14060942
]
Ray Chiang commented on YARN-2275:
----------------------------------
Oh, I see what you mean now. So, you'd prefer that a proper patch would grab
the full information from the configuration file (currently not possible)
rather than cobble together the two pieces of information (the config has the
proper host in one piece and the proper port, but not the proper IP, in another
piece).
Given that restriction, I'll agree that such a patch is not possible without
having the proper NM configuration info on the same node as the
JobHistoryServer.
And I'm open to other suggestions or compromises. I'd like to get something
that points to an understandable URL for customers rather than the "nothing at
this port" that the message currently provides.
> When log aggregation not enabled, message should point to NM HTTP port, not
> IPC port
> -------------------------------------------------------------------------------------
>
> Key: YARN-2275
> URL: https://issues.apache.org/jira/browse/YARN-2275
> Project: Hadoop YARN
> Issue Type: Bug
> Components: log-aggregation
> Affects Versions: 2.0.4-alpha
> Reporter: Sandy Ryza
> Assignee: Ray Chiang
> Labels: usability
> Attachments: MAPREDUCE5185-01.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
