[
https://issues.apache.org/jira/browse/KAFKA-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-6394.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
> Prevent misconfiguration of advertised listeners
> ------------------------------------------------
>
> Key: KAFKA-6394
> URL: https://issues.apache.org/jira/browse/KAFKA-6394
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Manikumar
> Priority: Major
> Fix For: 2.0.0
>
>
> We don't really have any protection from misconfiguration of the advertised
> listeners. Sometimes users will copy the config from one host to another
> during an upgrade. They may remember to update the broker id, but forget
> about the advertised listeners. It can be surprisingly difficult to detect
> this unless you know to look for it (e.g. you might just see a lot of
> NotLeaderForPartition errors as the fetchers connect to the wrong broker). It
> may not be totally foolproof, but it's probably enough for the common
> misconfiguration case to check existing brokers to see whether there are any
> which have already registered the advertised listener.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
