[
https://issues.apache.org/jira/browse/TEZ-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211326#comment-14211326
]
Siddharth Seth edited comment on TEZ-1775 at 11/13/14 9:33 PM:
---------------------------------------------------------------
Either a new log4j properties file, or potentially passing in additional
command line parameters without users having to setup everything.
Currently, trying to set a single log property - requires setting up the app
log dir, the log4j properties file as well as root logger settings. We should
at least be able to augment what is the default.
e.g. Continue using tez-container-log4j.properties, along with the yarn app dir
setup and tez.root.logger. Add in an additional property -
"tez.log.additional.properties" - which can be used to configure other aspects
of the logger. This may already be possible via tez-am-cmd-opts /
tez-task-cmd-opts. Need to check.
Open to other suggestions on how this can be simplified. The main pain point at
the moment is level DEBUG means tons of extra log messages which just create
noise.
was (Author: sseth):
Either a new log4j properties file, or potentially passing in additional
command line parameters without users having to setup everything.
Currently, trying to set a single log property - requires setting up the app
log dir, the log4j properties file as well as root logger settings. We should
at least be able to augment what is the default.
e.g. Continue using tez-container-log4j.properties, along with the yarn app dir
setup and tez.root.logger. Add in an additional property -
"tez.log.additional.properties" - which can be used to configure other aspects
of the logger. This may already be possible via tez-am-cmd-opts /
tez-task-cmd-opts. Need to check.
> Simpler task / AM logger configuration
> --------------------------------------
>
> Key: TEZ-1775
> URL: https://issues.apache.org/jira/browse/TEZ-1775
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Siddharth Seth
>
> Currently, it's fairly difficult to configure logging beyond a generic log
> level. It'll be useful to have some control over which components need to be
> logged at a level / should be avoided. The IPC layer, for example, generates
> a lot of (multi-line) noise - which isn't useful when looking for Tez logs
> only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
