[
https://issues.apache.org/jira/browse/KAFKA-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012616#comment-15012616
]
ASF GitHub Bot commented on KAFKA-2820:
---------------------------------------
GitHub user granders opened a pull request:
https://github.com/apache/kafka/pull/556
KAFKA-2820: Remove log threshold on appender in tools-log4j.properties
Removed a config in tools-log4j.properties which prevented certain service
classes from running at TRACE level.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/confluentinc/kafka
KAFKA-2820-systest-tool-loglevel
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/556.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #556
----
commit d58be9e6ed248882ef669e5d402dbb427a153eb7
Author: Geoff Anderson <[email protected]>
Date: 2015-11-19T01:53:52Z
Remove log threshold on appender in tools-log4j.properties
----
> System tests: log level is no longer propagating from service classes
> ---------------------------------------------------------------------
>
> Key: KAFKA-2820
> URL: https://issues.apache.org/jira/browse/KAFKA-2820
> Project: Kafka
> Issue Type: Bug
> Reporter: Geoff Anderson
> Assignee: Geoff Anderson
> Fix For: 0.9.1.0
>
>
> Many system test service classes specify a log level which should be
> reflected in the log4j output of the corresponding kafka tools etc.
> However, at least some these log levels are no longer propagating, which
> makes tests much harder to debug after they have run.
> E.g. KafkaService specifies a DEBUG log level, but all collected log output
> from brokers is at INFO level or above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
