[
https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15153519#comment-15153519
]
Robert Kanter commented on YARN-4701:
-------------------------------------
A few comments:
- When {{getApplicationLogURL()}} returns null, "null" is going to get printed
as part of the error message. Instead, we should either omit the message or
say something more helpful.
- Don't hardcode "http://";. Instead, do something like
https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/webapp/util/WebAppUtils.java#L255
so that https is properly handled if it's enabled.
> When task logs are not available, port 8041 is referenced instead of port 8042
> ------------------------------------------------------------------------------
>
> Key: YARN-4701
> URL: https://issues.apache.org/jira/browse/YARN-4701
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Reporter: Haibo Chen
> Assignee: Haibo Chen
> Attachments: yarn4701.001.patch
>
>
> Accessing logs for an task attempt in the workflow tool in Hue shows "Logs
> not available for attempt_1433822010707_0001_m_000000_0. Aggregation may not
> be complete, Check back later or try the nodemanager at
> quickstart.cloudera:8041"
> If the user follows that link, he/she will get "It looks like you are making
> an HTTP request to a Hadoop IPC port. This is not the correct port for the
> web interface on this daemon."
> We should update the message to use the correct HTTP port. We could also make
> it more convenient by providing the application's specific page at NM as well
> instead of just NM's main page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
