[
https://issues.apache.org/jira/browse/KAFKA-13679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500307#comment-17500307
]
Philip Bourke commented on KAFKA-13679:
---------------------------------------
[~hachikuji] I believe you made this change? Do you have an opinion on this?
Apologies if I have the wrong person.
> Superfluous node disconnected log messages
> ------------------------------------------
>
> Key: KAFKA-13679
> URL: https://issues.apache.org/jira/browse/KAFKA-13679
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 3.1.0
> Reporter: Philip Bourke
> Priority: Minor
>
> In Kafka 3.1 the "{_}Node x disconnected{_}" log message in the
> {{NetworkClient.java}} class was changed from DEBUG to INFO -
> [https://github.com/apache/kafka/commit/79d97bd29d059e8ba8ee7726b49d76e03e281059#diff-dcc1af531d191de8da1e23ad6d878a3efc463ba4670dbcf2896295a9dacd1c18R935]
> Now my application logs are full of node disconnected messages and it would
> indicate that there may be a connectivity problem. However I can see that the
> logs are getting written every 5 minutes exactly, and it's the AdminClient
> that is writing the logs.
> {code:bash}
> 2022-02-16 14:45:39,277 [d-60105f051cdb-admin] INFO
> o.apache.kafka.clients.NetworkClient - [AdminClient
> clientId=desktop-session-internal-user-streamer-v1-9888ff1d-446e-40cd-88dd-60105f051cdb-admin]
> Node 1 disconnected.
> {code}
> My guess is that it may be the
> [connections.max.idle.ms|https://kafka.apache.org/documentation/#adminclientconfigs_connections.max.idle.ms]
> config setting, and there is in fact no issue with connectivity to the
> brokers?
> I'm raising this ticket here because the logs are full of these repetitive
> messages indicating an issue and setting off alarm bells, and also because I
> did not get a response on the confluent forum or in any slack channels.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
