[
https://issues.apache.org/jira/browse/KAFKA-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954436#comment-13954436
]
Guozhang Wang commented on KAFKA-1350:
--------------------------------------
[~jjkoshy] Could you provide some more context? I thought the state change
logging is guarded by log4j?
> Fix excessive state change logging
> ----------------------------------
>
> Key: KAFKA-1350
> URL: https://issues.apache.org/jira/browse/KAFKA-1350
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.1
> Reporter: Joel Koshy
> Priority: Blocker
> Fix For: 0.8.1.1
>
>
> I can provide steps to reproduce this issue. The state change logger needs
> to be guarded (to check if trace logging is turned on or not).
> The delete topic patch significantly increased the amount of logging that we
> do both on the controller. This results in higher latencies in state
> transitions and can slow down the controller (as well as the broker). This
> slow-down was how we ran into KAFKA-1342.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
