ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13813) After kerberization, Kafka brokers fail to start
Date Wed, 11 Nov 2015 16:50:11 GMT

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

Hudson commented on AMBARI-13813:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #3811 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3811/])
AMBARI-13813 After kerberization, Kafka brokers fail to start (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9c5e8844ae68a6ce07a5260182fe41243e3bad38])
* ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
* ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java
AMBARI-13813 After kerberization, Kafka brokers fail to start (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1ca59255ed13e615dfddeffa3b3660f5cb6dbb90])
* ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java
* ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java


> After kerberization, Kafka brokers fail to start
> ------------------------------------------------
>
>                 Key: AMBARI-13813
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13813
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-upgrade, stacks
>    Affects Versions: 2.1.2
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13813-trunk.patch
>
>
> PROBLEM:  After Ambari upgrade and kerberization, Kafka broker does not come up.  Following
error is observed:
> FATAL Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)

> java.lang.IllegalArgumentException: You must pass java.security.auth.login.config in
secure mode.
> STEPS TO REPRODUCE:  Upgrade Ambari to 2.1.2 on a cluster without kerberization and with
Kafka brokers, then kerberize through Ambari.
> EXPECTED RESULT:  Kafka broker comes up successfully, and ambari sets the correct parameters
in kafka-env.sh:
> {code}
> export KAFKA_KERBEROS_PARAMS="-Djava.security.auth.login.config=/etc/kafka/conf/kafka_jaas.conf"

> {code}
> ACTUAL RESULT:  Kafka broker fails to come up and ambari-server set kafka-env incorrectly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message