You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/12/20 20:57:00 UTC

[jira] [Created] (KAFKA-6394) Prevent misconfiguration of advertised listeners

Jason Gustafson created KAFKA-6394:
--------------------------------------

             Summary: 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


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
(v6.4.14#64029)