[
https://issues.apache.org/jira/browse/MAPREDUCE-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli moved YARN-647 to MAPREDUCE-5700:
---------------------------------------------------------
Target Version/s: (was: 2.3.0)
Affects Version/s: (was: 2.2.0)
(was: 2.0.4-alpha)
(was: 0.23.7)
0.23.7
2.0.4-alpha
2.2.0
Key: MAPREDUCE-5700 (was: YARN-647)
Project: Hadoop Map/Reduce (was: Hadoop YARN)
> historyServer can't show container's log when aggregation is not enabled
> ------------------------------------------------------------------------
>
> Key: MAPREDUCE-5700
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5700
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 2.2.0, 2.0.4-alpha, 0.23.7
> 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-2.patch, 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.5#6160)
