[
https://issues.apache.org/jira/browse/TEZ-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725787#comment-14725787
]
Hitesh Shah commented on TEZ-2744:
----------------------------------
bq. Suppress RackResolver lines (this shows up multiple times for the same host
which may indicate that caching is not being used)
Follow up jira for this?
bq. TaskAttemptImpl - logging of TaskSpec in AM
Maybe follow same approach as what is mentioned later. Log if taskSpec is
different from the vertex spec? How do we handle root input assignment
debugging? Just set at debug level and let users do one off debugging?
Agreed on most of the other recommendations.
> 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)
