Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-15801

improve Kafka broker/NetworkClient logging for connectivity issues with hostname and port info and higher severity

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: In Progress
    • Trivial
    • Resolution: Unresolved
    • 3.6.0
    • None
    • logging
    • None

    Description

      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)

       

      Attachments

        Activity

          People

            johndoe johndoe
            alexanderkilian Alexander Kilian
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: