You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2016/08/03 17:38:20 UTC
[jira] [Commented] (AMBARI-17694) Kafka listeners property does not
show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406283#comment-15406283 ]
Robert Levas commented on AMBARI-17694:
---------------------------------------
[~harsha_ch], [~anitajebaraj]...
The problem with the original patch is not related to the stack advisor. Essentially there are two kerberos.json files for KAFKA.
* {{…/stacks/HDP/2.5/services/KAFKA/kerberos.json}}
* {{…/resources/common-services/KAFKA/0.9.0/kerberos.json}}
The patch updates the kerberos.json file in common-service ({{…/resources/common-services/KAFKA/0.9.0/kerberos.json}}); however, the kerberos.json file that comes into play with installing HDP 2.5 is the one at {{…/stacks/HDP/2.5/services/KAFKA/kerberos.json}}.
So the same change make to {{…/resources/common-services/KAFKA/0.9.0/kerberos.json}} should also be made to {{…/stacks/HDP/2.5/services/KAFKA/kerberos.json}}. Unless, the Kafka version installed for pre-HDP 2.5 stacks does not need it.
> Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-17694
> URL: https://issues.apache.org/jira/browse/AMBARI-17694
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Anita Gnanamalar Jebaraj
> Assignee: Anita Gnanamalar Jebaraj
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17694-1.patch, AMBARI-17694-Jul26.patch, AMBARI-17694.patch
>
>
> When kerberos is enabled, the protocol for listeners in /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, even though the Ambari UI shows otherwise
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)