You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Axton Grams (JIRA)" <ji...@apache.org> on 2017/06/19 03:57:00 UTC

[jira] [Created] (AMBARI-21275) Kafka advertised.listeners can't be configured when security is enabled

Axton Grams created AMBARI-21275:
------------------------------------

             Summary: Kafka advertised.listeners can't be configured when security is enabled
                 Key: AMBARI-21275
                 URL: https://issues.apache.org/jira/browse/AMBARI-21275
             Project: Ambari
          Issue Type: Bug
          Components: ambari-sever
    Affects Versions: 2.4.2
            Reporter: Axton Grams


When running Kafka Broker on a multi-homed, secure (kerberized) host, it is necessary to set the following configuration parameters:

advertised.listeners=PLAINTEXTSASL://host.domain.tld:6667
listeners=PLAINTEXTSASL://0.0.0.0:6667

This configuration is not achievable due to limitations of the Ambari Server scripts that generate the Kafka Broker configuration file.

The attached patch corrects this issue.  The patch does a few things:
- maintains consistency in behavior in updating protocol in advertised.listeners to match the behavior of existing parameter, 'listeners'
- sets advertised.listeners to the listeners if it is not defined in Ambari
- replaces the literal 'localhost' with the actual hostname; this is consistent with the behavior of the existing parameter, 'listeners'



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)