[
https://issues.apache.org/jira/browse/AMBARI-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-11634:
------------------------------------
Priority: Critical (was: Major)
> Kafka Service Check completes successfully however the stdout indicates an
> error creating a previously created topic
> --------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-11634
> URL: https://issues.apache.org/jira/browse/AMBARI-11634
> Project: Ambari
> Issue Type: Bug
> Environment: ambari-2.1.0-854, hdp-2.3.0.0-2216, sles11sp3
> Reporter: Zack Marsh
> Assignee: Sriharsha Chintalapani
> Priority: Critical
> Fix For: 2.2.0
>
>
> The Kafka Service Check is consistently "passing" yet the stdout indicates a
> failure due to Kafka attempting to create the topic named 'test' which
> already exists.
> Stdout as seen in Ambari for the Kafka Service Check operation:
> stdout:
> {code}
> False
> 2015-06-02 18:20:22,792 - Running kafka create topic command: source
> /usr/hdp/current/kafka-broker/config/kafka-env.sh ;
> /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper
> piripiri1.labs.teradata.com:2181,piripiri3.labs.teradata.com:2181,piripiri2.labs.teradata.com:2181
> --create --topic ambari_kafka_service_check --partitions 1
> --replication-factor 1
> Error while executing topic command Topic "ambari_kafka_service_check"
> already exists.
> kafka.common.TopicExistsException: Topic "ambari_kafka_service_check" already
> exists.
> at
> kafka.admin.AdminUtils$.createOrUpdateTopicPartitionAssignmentPathInZK(AdminUtils.scala:248)
> at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:233)
> at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:92)
> at kafka.admin.TopicCommand$.main(TopicCommand.scala:54)
> at kafka.admin.TopicCommand.main(TopicCommand.scala)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
