You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2016/10/07 17:02:20 UTC
[jira] [Updated] (KAFKA-1592) Some INFO level logging needs to be
DEBUG
[ https://issues.apache.org/jira/browse/KAFKA-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson updated KAFKA-1592:
-----------------------------------
Fix Version/s: (was: 0.10.1.0)
> Some INFO level logging needs to be DEBUG
> -----------------------------------------
>
> Key: KAFKA-1592
> URL: https://issues.apache.org/jira/browse/KAFKA-1592
> Project: Kafka
> Issue Type: Bug
> Reporter: Guozhang Wang
> Assignee: Mayuresh Gharat
> Labels: newbie
>
> Some of the INFO level log4j entries are not really useful, for example in SocketServer.Processor, due to metadata requests that reply on a separate and short-lived socket, the following log can be constantly printed:
> info("Closing socket connection to %s.".format(channelFor(key).socket.getInetAddress))
> We'd better move them to DEBUG if they are expected in normal state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)