You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Manikumar (JIRA)" <ji...@apache.org> on 2018/02/07 09:46:00 UTC

[jira] [Commented] (AMBARI-20908) Kafka advertised.listeners replaced in Kerberos Mode

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

Manikumar commented on AMBARI-20908:
------------------------------------

This got merged https://github.com/apache/ambari/commit/feb6f7d9096ffc284bdc89f09035d289a1d73d48

> 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
>            Priority: Major
>             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
(v7.6.3#76005)