[
https://issues.apache.org/jira/browse/KAFKA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527584#comment-16527584
]
Luan Cestari commented on KAFKA-7111:
-------------------------------------
Thank you for finding the root cause. Do you think make sense change log
level of that line for cases like this one? I mean, in production it might
happen if it send an hostname which is configured only in the Kafka broker
right?
About the other issues, do you think it would to open other jira issues to
address them. I am not sure if it really is Kafka client the root cause of
them and maybe it is working as intended.
On Fri, Jun 29, 2018, 9:47 AM Stanislav Kozlovski (JIRA) <[email protected]>
> 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
>
> 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)
