[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816216#comment-13816216
]
Zhijie Shen commented on YARN-647:
----------------------------------
{code}
+ if (!aggregation) {
+ logsLink = join(HttpConfig.getSchemePrefix(), nodeHttpAddr,
+ "/node", "/containerlogs/",
+ containerIdString, "/", app.getJob().getUserName());
{code}
I'm afraid this link will not work as well. When a container is stopped, NM
local logs will be deleted and not be accessible via webUI or service again.
However, I'm afraid "Try the nodemanager at ..." is a bit misleading as well,
which makes users think that the logs are available via NM webUI. The fact is
that for debugging purpose, we can config
"yarn.nodemanager.delete.debug-delay-sec" to delay the deletion of NM local
logs, but it's not user-oriented, and anyway, they're not accessible via web.
Maybe we want to remove misleading words here?
> historyServer can't show container's log when aggregation is not enabled
> ------------------------------------------------------------------------
>
> Key: YARN-647
> URL: https://issues.apache.org/jira/browse/YARN-647
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 0.23.7, 2.0.4-alpha, 2.2.0
> Environment: yarn.log-aggregation-enable=false , HistoryServer will
> show like this:
> Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669
> Reporter: shenhong
> Assignee: shenhong
> Attachments: yarn-647.patch
>
>
> When yarn.log-aggregation-enable is seted to false, after a MR_App complete,
> we can't view the container's log from the HistoryServer, it shows message
> like:
> Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669
> Since we don't want to aggregate the container's log, because it will be a
> pressure to namenode. but sometimes we also want to take a look at
> container's log.
> Should we show the container's log across HistoryServer even if
> yarn.log-aggregation-enable is seted to false.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
