ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-17479) not being set on secure kafka clusters
Date Wed, 06 Jul 2016 00:21:11 GMT


Hadoop QA commented on AMBARI-17479:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results:
Console output:

This message is automatically generated.

> not being set on secure kafka clusters
> ------------------------------------------------------------
>                 Key: AMBARI-17479
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>              Labels: kerberos, kerberos_descriptor, stack_advisor
>             Fix For: 2.4.0
>         Attachments: AMBARI-17479_branch-2.4_01.patch, AMBARI-17479_trunk_01.patch
> The {{kafka-broker/}} property is not being set properly when Kerberos
is enabled.
> The following logic should be followed:
> {noformat}
> if Kerberos is enabled
>   if ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled == yes
>     set to "org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer"
>   else
>     set to ""
> else
>   remove
> {noformat}
> This should be updated in the stack advisor code. 
> While at it, configurations from Kafka's {{kerberos.json}} file should be moved to the
stack advisor to help ensure properties are set in the the same place to help with code maintenance
and consistency.

This message was sent by Atlassian JIRA

View raw message