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/25 19:00:08 UTC

[jira] [Comment Edited] (KAFKA-2079) Support exhibitor

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

Helena Edelson edited comment on KAFKA-2079 at 9/25/15 4:59 PM:
----------------------------------------------------------------

[~joestein] Thanks. +1 Low handing fruit like async watchers and leader election can be accomplished many ways, for instance with Akka + Akka Cluster. Pros and cons of course with any plugable solution.
It may be nice to allow the meta data storage API to be separate, so that for instance Cassandra could be used or other desired technology that perhaps is already in one's distributed system.  
The actual implementations will be less trivial than the design of plugability itself :-) I'll watch for the start of the discussion on the list.


was (Author: helena_e):
[~joestein] Thanks. +1 and 

Low handing fruit like async watchers and leader election can be accomplished many ways, for instance with Akka + Akka Cluster. Pros and cons of course with any plugable solution.
It may be nice to allow the meta data storage API to be separate, so that for instance Cassandra could be used or other desired technology that perhaps is already in one's distributed system.  
The actual implementations will be less trivial than the design of plugability itself :-) I'll watch for the start of the discussion on the list.

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