You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2017/05/10 11:42:04 UTC

[jira] [Commented] (AMBARI-20434) Enhance Kafka Service Check

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

Dmitry Lysnichenko commented on AMBARI-20434:
---------------------------------------------

Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
   9abfcf2..80ef772  trunk -> trunk


> 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)