[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816005#comment-13816005
]
Hadoop QA commented on YARN-647:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581885/yarn-647.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2390//console
This message is automatically generated.
> 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)
