Michael Bingham created KAFKA-12456:
---------------------------------------
Summary: Log "Listeners are not identical across brokers" message
at WARN/INFO instead of ERROR
Key: KAFKA-12456
URL: https://issues.apache.org/jira/browse/KAFKA-12456
Project: Kafka
Issue Type: Improvement
Components: core, security
Affects Versions: 2.6.1, 2.7.0
Reporter: Michael Bingham
Currently, when listeners are not identical across brokers, an {{ERROR}} level
log message is generated like:
{code:java}
[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) {code}
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 .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
