[
https://issues.apache.org/jira/browse/AMBARI-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004583#comment-16004583
]
Hudson commented on AMBARI-20434:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7449 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7449/])
AMBARI-20434. Enhance Kafka Service Check (WangJie via dlysnichenko)
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=80ef77299855f4f1c6a0aceed9cee9ee93c22da1])
* (edit)
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/service_check.py
* (edit)
ambari-server/src/main/resources/common-services/KAFKA/0.9.0/configuration/kafka-broker.xml
> Enhance Kafka Service Check
> ---------------------------
>
> Key: AMBARI-20434
> URL: https://issues.apache.org/jira/browse/AMBARI-20434
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk
> Reporter: WangJie
> Assignee: Dmitry Lysnichenko
> Fix For: trunk
>
> Attachments: AMBARI-20434.patch
>
>
> Problem:
> Kafka Service Check will create the kafka topic only if the topic doesn't
> exist.
> if it exists, Kafka Service Check will return success directly.
> After topic is being created, we sense that each time running service check
> will not reflect the kafka actual state correctly
> Suggestion:
> Every running kafka service check, delete the existed topic and recreate it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
