Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5692C17956 for ; Wed, 3 Jun 2015 00:16:31 +0000 (UTC) Received: (qmail 6687 invoked by uid 500); 2 Jun 2015 22:29:51 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 6657 invoked by uid 500); 2 Jun 2015 22:29:51 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 6580 invoked by uid 99); 2 Jun 2015 22:29:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jun 2015 22:29:51 +0000 Date: Tue, 2 Jun 2015 22:29:51 +0000 (UTC) From: "Zack Marsh (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-11634) Kafka Service Check completes successfully however the stdout indicates an error creating a previously created topic MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Zack Marsh created AMBARI-11634: ----------------------------------- Summary: 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 Priority: Minor 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)