You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Alexander Kilian (Jira)" <ji...@apache.org> on 2023/11/09 13:29:00 UTC
[jira] [Created] (KAFKA-15801) improve Kafka broker/NetworkClient logging for connectivity issues
Alexander Kilian created KAFKA-15801:
----------------------------------------
Summary: improve Kafka broker/NetworkClient logging for connectivity issues
Key: KAFKA-15801
URL: https://issues.apache.org/jira/browse/KAFKA-15801
Project: Kafka
Issue Type: Improvement
Components: logging
Affects Versions: 3.6.0
Reporter: Alexander Kilian
When a component of the Kafka broker tries to reach another broker within the cluster the logging should be more elaborate and include the IP/hostname and port it tries to connect to, and have a higher severity WARN rather than INFO.
Current logging:
{{[2023-11-09 07:33:36,106] INFO [TransactionCoordinator id=1] Disconnecting from node 1 due to socket connection setup timeout. The timeout value is 26590 ms. (org.apache.kafka.clients.NetworkClient)}}
Suggested logging:
{{[2023-11-09 07:33:36,106] WARN [TransactionCoordinator id=1] Disconnecting from node 1 on kafka-headless.m2-mgex.svc.cluster.local:9093 due to socket connection setup timeout. The timeout value is 26590 ms. (org.apache.kafka.clients.NetworkClient)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)