You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2015/11/10 15:35:10 UTC
[jira] [Created] (AMBARI-13813) After kerberization, Kafka brokers
fail to start
Dmytro Sen created AMBARI-13813:
-----------------------------------
Summary: 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: stacks
Affects Versions: 2.1.2
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 2.1.3
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)