You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Brahma Reddy Battula (JIRA)" <ji...@apache.org> on 2014/12/24 14:03:13 UTC
[jira] [Commented] (MAPREDUCE-6203) if log-aggregation is enable
and run some MR job, the AM log will be aggregated.then disable it,then in
MR JobHistoryServer and YARN RM UI link,the AM log cannot be visible
[ https://issues.apache.org/jira/browse/MAPREDUCE-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258228#comment-14258228 ]
Brahma Reddy Battula commented on MAPREDUCE-6203:
-------------------------------------------------
HI huangyitian,
Turning on log aggregation allows users to easily store container logs in HDFS and subsequently view them in the YARN web UIs from a central place.
If *yarn.log-aggregation-enable* is disabled try looking for the logs under each nodemanager that ran the tasks.
The location for this local dir is configured as property *yarn.nodemanager.log-dirs* in yarn-site.xml
SO if you want to view from JHS and YARN Web UI then enable log aggregation..
> if log-aggregation is enable and run some MR job, the AM log will be aggregated.then disable it,then in MR JobHistoryServer and YARN RM UI link,the AM log cannot be visible
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6203
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6203
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 2.4.1
> Reporter: huangyitian
> Priority: Minor
>
> as the Summary description, I think for the MR JobHistory Server, should not let “yarn.log-aggregation-enable” affect the history job,even “yarn.log-aggregation-enable” is false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)