[
https://issues.apache.org/jira/browse/TEZ-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983267#comment-14983267
]
Siddharth Seth commented on TEZ-2917:
-------------------------------------
[~sershe] - there have been a couple other jiras which try cleaning up logs.
TEZ-2774, TEZ-2775. Some of these changes are even more aggressive than the
ones on that jira. Many of the log lines become useful when things break. A lot
of them show up once per task. Some of them though show up multiple times per
task - and cause far more noise.
Wondering if there's some other way to control these noisy lines. One would be
to go and move a large chunk of the logging to TRACE, and move such lines to
DEBUG. Another would be to use a cusom LOGGER for such lines - so that they can
be turned off via logging configuration when required.
> change some logs from info to debug
> -----------------------------------
>
> Key: TEZ-2917
> URL: https://issues.apache.org/jira/browse/TEZ-2917
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: TEZ-2917.patch
>
>
> I've done a highly unscientific summarization of the logs from some random
> queries, and will now change some log statements that are the most prevalent
> and not extremely useful from info to debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
