You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2015/09/06 09:08:45 UTC
[jira] [Comment Edited] (TEZ-2744) Logging cleanup and enhancements
[ https://issues.apache.org/jira/browse/TEZ-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732239#comment-14732239 ]
Jeff Zhang edited comment on TEZ-2744 at 9/6/15 7:07 AM:
---------------------------------------------------------
* History event occupy a large proportion of the log. Any consideration to move it into separated files ? IMO, the history events is more likely for offline analytics rather than for human diagnostics.
* Should suppress yarn related log (configure them as debug in log4j.properties ) ? like the following
{noformat}
[INFO] [AMRM Heartbeater thread]|| impl.AMRMClientImpl Received new token for : cn044-10.l42scl.hortonworks.com:49522
:2015-09-06 06:38:03,874 [INFO] [ContainerLauncher #15]|| impl.ContainerManagementProtocolProxy Opening proxy : cn048-10.l42scl.hortonworks.com:35632
:2015-09-06 06:38:03,874 [INFO] [ContainerLauncher #10]|| impl.ContainerManagementProtocolProxy Opening proxy : cn048-10.l42scl.hortonworks.com:35632
{noformat}
was (Author: zjffdu):
History event occupy a large proportion of the log. Any consideration to move it into separated files ? IMO, the history events is more likely for offline analytics rather than for human diagnostics.
> Logging cleanup and enhancements
> --------------------------------
>
> Key: TEZ-2744
> URL: https://issues.apache.org/jira/browse/TEZ-2744
> Project: Apache Tez
> Issue Type: Improvement
> Affects Versions: 0.5.0
> Reporter: Siddharth Seth
>
> There's far too much logging, some of which is redundant information - which leads to large log files for jobs.
> Also, some logging can be enhanced to include additional context.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)