You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Helena Edelson (JIRA)" <ji...@apache.org> on 2015/09/24 12:01:19 UTC

[jira] [Commented] (KAFKA-2079) Support exhibitor

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

Helena Edelson commented on KAFKA-2079:
---------------------------------------

[~joestein] Is there a ticket for the dependency work 'separating out the meta data storage and consensus service (async watchers and leader election)' yet? I am unable to find - or perhaps this is still in the discussion phase...

> Support exhibitor
> -----------------
>
>                 Key: KAFKA-2079
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2079
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Aaron Dixon
>
> Exhibitor (https://github.com/Netflix/exhibitor) is a discovery/monitoring solution for managing Zookeeper clusters. It supports use cases like discovery, node replacements and auto-scaling of Zk cluster hosts (so you don't have to manage a fixed set of Zk hosts--especially useful in cloud environments.)
> The easiest way for Kafka to support connection to Zk clusters via exhibitor is to use curator as its client. There is already a separate ticket for this: KAFKA-873



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)