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

Log "Listeners are not identical across brokers" message at WARN/INFO instead of ERROR

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Patch Available
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.7.0, 2.6.1, 2.8.0
    • Fix Version/s: None
    • Component/s: core, security
    • Labels:
      None

      Description

      Currently, when listeners are not identical across brokers, an ERROR level log message is generated like:

       [2021-03-11 20:25:18,881] ERROR [MetadataCache brokerId=0] Listeners are not identical across brokers: LongMap(0 -> Map(ListenerName(PLAINTEXT) -> 192.168.111.99:9092 (id: 0 rack: null), ListenerName(SSL) -> 192.168.111.99:9094 (id: 0 rack: null), ListenerName(SASL_PLAINTEXT) -> 192.168.111.99:9093 (id: 0 rack: null)), 2 -> Map(ListenerName(PLAINTEXT) -> 192.168.116.148:9092 (id: 2 rack: null), ListenerName(SASL_PLAINTEXT) -> 192.168.116.148:9093 (id: 2 rack: null)), 1 -> Map(ListenerName(PLAINTEXT) -> 192.168.111.100:9092 (id: 1 rack: null), ListenerName(SASL_PLAINTEXT) -> 192.168.111.100:9093 (id: 1 rack: null))) (kafka.server.MetadataCache) 

      When adding security incrementally with a rolling update, this event is normal/expected, so recommend lowering the log level for this message to WARN or INFO  to avoid confusion.

      This log message was originally added with https://issues.apache.org/jira/browse/KAFKA-6501 . 

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mikebin Michael Bingham
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: