[
https://issues.apache.org/jira/browse/KAFKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378603#comment-15378603
]
Sriharsha Chintalapani commented on KAFKA-3948:
-----------------------------------------------
[~bharatviswa] [~gquintana] host and port in zookeeper data is used to maintain
the backward compatibility. So only plaintext port and host will be registered
there. If you are depending zookeeper data to parse broker hosts I suggest you
to look under endpoints section.
> Invalid broker port in Zookeeper when SSL is enabled
> ----------------------------------------------------
>
> Key: KAFKA-3948
> URL: https://issues.apache.org/jira/browse/KAFKA-3948
> Project: Kafka
> Issue Type: Bug
> Components: core, network
> Affects Versions: 0.9.0.1
> Reporter: Gérald Quintana
> Assignee: Bharat Viswanadham
>
> With broker config
> {code}
> listeners=SSL://:9093,PLAINTEXT://:9092
> port=9093
> {code}
> gives in Zookeeper /brokers/ids/1
> {code}
> {"jmx_port":9999,"timestamp":"1468249905473","endpoints":["SSL://kafka1:9093","PLAINTEXT://kafka1:9092"],"host":"kafka1","version":2,"port":9092}
> {code}
> Notice that port 9092 not 9093
> Then, different scenario, with config:
> {code}
> listeners=SSL://:9093
> port=9093
> {code}
> gives in Zookeeper /brokers/ids/1
> {code}
> {"jmx_port":9999,"timestamp":"1468250372974","endpoints":["SSL://kafka1:9093"],"host":null,"version":2,"port":-1}
> {code}
> Now host is null and port is -1
> Setting advertised.port doesn't help
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
