You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Rajini Sivaram (JIRA)" <ji...@apache.org> on 2018/06/29 14:40:00 UTC

[jira] [Resolved] (KAFKA-7111) Review the NetworkClient log level used

     [ https://issues.apache.org/jira/browse/KAFKA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajini Sivaram resolved KAFKA-7111.
-----------------------------------
       Resolution: Fixed
         Reviewer: Rajini Sivaram
    Fix Version/s: 2.0.0

> Review the NetworkClient log level used
> ---------------------------------------
>
>                 Key: KAFKA-7111
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7111
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients
>            Reporter: Luan Cestari
>            Assignee: Stanislav Kozlovski
>            Priority: Trivial
>             Fix For: 2.0.0
>
>
> Hi,
>  
> I was using Kafka on some projects and unfortunately I had to use Debug (and some times even Trace) log level to see some issues. One of the most recently cases was: 
> [https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/NetworkClient.java#L872]
>  
> If I got the name of the broker and it is unreachable, the errors should be more severe than "DEBUG" level IMHO. I would at least put a INFO level for this case or ERROR level (which seems to fit better but I don't know the practices used in the project).
>  
> Thank you in advance
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)