[
https://issues.apache.org/jira/browse/KAFKA-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007706#comment-15007706
]
ASF GitHub Bot commented on KAFKA-2820:
---------------------------------------
GitHub user granders opened a pull request:
https://github.com/apache/kafka/pull/538
KAFKA-2820: systest log level
This restores control over log level in KafkaService, and adds SASL debug
logging when SASL is enabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/confluentinc/kafka
KAFKA-2820-systest-log-level
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/538.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 #538
----
commit 0f27b3b547226d20dc7161acf02753ebbe9b5235
Author: Geoff Anderson <ge...@confluent.io>
Date: 2015-11-17T00:38:44Z
Add debug logging for SASL
commit 0fc43371e3094cdb9df336430ed5145490b0010c
Author: Geoff Anderson <ge...@confluent.io>
Date: 2015-11-17T00:39:04Z
Restore control over log level in KafkaService
----
> 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
>
> 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)
