[
https://issues.apache.org/jira/browse/AMBARI-20908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993381#comment-15993381
]
Bharat Viswanadham commented on AMBARI-20908:
---------------------------------------------
With the patch one issue it will happen is if User has manually set listeners
to advertised.listeners=PLAINTEXT://<<hostname>>:<<port>>, after enable
kerberos, the user has to manually change the advertised.listeners to
SASL_PLAINTEXT://<<hostname>>:<<port>>. Might be that is the reason in the code
to use advertised.listeners as listeners. Any idea's on how to handle the user
manually set case also?
> Kafka advertised.listeners replaced in Kerberos Mode
> ----------------------------------------------------
>
> Key: AMBARI-20908
> URL: https://issues.apache.org/jira/browse/AMBARI-20908
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Fix For: trunk
>
> Attachments: AMBARI-20908.PATCH
>
>
> Install ambari with Kafka.
> 1. Add advertised.listeners to Kafka Config.
> 2. Restart Kafka.
> 3. Enable Kerberos.
> 4. After that advertised.listeners get replaced with listeners.
> This is happening, because of the code in common services in kafka.py. Even
> if advertised.listeners is not set, it automatically add's
> advertised.listeners to kafka config, which has same values as
> if params.security_enabled and params.kafka_kerberos_enabled:
> Logger.info("Kafka kerberos security is enabled.")
> kafka_server_config['advertised.listeners'] = listeners
> Logger.info(format("Kafka advertised listeners: {listeners}"))
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
