You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Ambud Sharma (JIRA)" <ji...@apache.org> on 2017/06/17 03:35:02 UTC

[jira] [Resolved] (AMBARI-20688) Supvervisord control option for Kafka broker

     [ https://issues.apache.org/jira/browse/AMBARI-20688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ambud Sharma resolved AMBARI-20688.
-----------------------------------
    Resolution: Workaround

Using ambari autorestart feature as an alternative. Stack override code is available here:

https://github.com/ambud/ambari-kafka-supervisord

> Supvervisord control option for Kafka broker
> --------------------------------------------
>
>                 Key: AMBARI-20688
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20688
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.4.1
>            Reporter: Ambud Sharma
>
> Just like Storm Supervisor option in Storm Ambari stack to have Supervisord manage the process, adding supervisord for Kafka is helpful for automated broker recovery in case of machine reboots.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)