Details
-
Improvement
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
0.23.7, 2.0.4-alpha, 2.2.0
-
None
-
None
-
yarn.log-aggregation-enable=false , HistoryServer will show like this:
Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669
Description
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.