[
https://issues.apache.org/jira/browse/KAFKA-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoff Anderson updated KAFKA-2820:
----------------------------------
Description:
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.
was:
Many system test service classes specify a log level which should be reflected
in the log4j output of the corresponding kafka tools etc.
However, 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.
> 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)
