[
https://issues.apache.org/jira/browse/KAFKA-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15662381#comment-15662381
]
Ewen Cheslack-Postava commented on KAFKA-4021:
----------------------------------------------
[~junrao] Is this actually reasonable to do across the board for the Kafka
service? Normally trace-level logs incur enough overhead that they can affect
normal behavior and, e.g., could drastically affect anything trying to get
performance stats.
> system tests need to enable trace level logging for controller and
> state-change log
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-4021
> URL: https://issues.apache.org/jira/browse/KAFKA-4021
> Project: Kafka
> Issue Type: Improvement
> Components: system tests
> Affects Versions: 0.10.0.0
> Reporter: Jun Rao
> Assignee: Geoff Anderson
>
> We store detailed information about leader changes at trace level in the
> controller and the state-change log. Currently, our system tests only collect
> debug level logs. It would be useful to collect trace level logging for these
> two logs and archive them if there are test failures, at least for
> replication related tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
