[jira] [Commented] (KAFKA-4260) Improve documentation of configuration listeners=PLAINTEXT://0.0.0.0:9092

["David Watzke (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15551925#comment-15551925 ] 

David Watzke commented on KAFKA-4260:
-------------------------------------

Also quite disturbing was the fact that there was no relevant error message in logs that would tell us what the hell was happening - that should be addressed as well. Thanks.

> Improve documentation of configuration listeners=PLAINTEXT://0.0.0.0:9092
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-4260
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4260
>             Project: Kafka
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 0.10.0.1
>            Reporter: Michal Turek
>            Priority: Minor
>
> We have just updated our testing Kafka cluster to 0.10 and we were facing one issue with migration of legacy 0.8 configuration to
> {noformat}
> listeners=PLAINTEXT://0.0.0.0:9092
> # advertised.listeners=PLAINTEXT://myPublicHostName:9092    # REQUIRED for 0.0.0.0:9092
> {noformat}
> This configuration will be invalid if {{advertised.listeners}} is not set too. Connection string 0.0.0.0:9092 is stored to ZooKeeper according to documentation of  {{advertised.listeners}} and observed behavior, but it isn't obvious and difficult to analyze. Clients and even other brokers try to communicate with brokers using destination address 0.0.0.0:9092, which is impossible. Specification of {{advertised.listeners}} as shown above fixed the issue.
> Please update documentation at http://kafka.apache.org/0100/documentation#brokerconfigs and backport the change to 0.9 and 0.10 branches.
> h4. advertised.listeners
> Listeners to publish to ZooKeeper for clients to use, if different than the *`listeners`* -above-. In IaaS environments, this may need to be different from the interface to which the broker binds. If this is not set, the value for `listeners` will be used.
> h4. listeners
> Listener List - Comma-separated list of URIs we will listen on and their protocols. Specify hostname as 0.0.0.0 to bind to all interfaces *(note `advertised.listeners` configuration is required for 0.0.0.0)*. Leave hostname empty to bind to default interface. Examples of legal listener lists: PLAINTEXT://myhost:9092,TRACE://:9091 PLAINTEXT://0.0.0.0:9092, TRACE://localhost:9093



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)