[
https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shenhong updated YARN-647:
--------------------------
Environment:
yarn.log-aggregation-enable=false
Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669
was:
When yarn.log-aggregation-enable was 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
> historyServer can 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
> Components: documentation
> Affects Versions: 0.23.7, 2.0.4-alpha
> Environment: yarn.log-aggregation-enable=false
> Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669
> Reporter: shenhong
>
> When yarn.log-aggregation-enable was 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 was seted to false.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
