You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Joe Stein (JIRA)" <ji...@apache.org> on 2015/04/02 01:01:01 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=14391680#comment-14391680 ]
Joe Stein commented on KAFKA-2079:
----------------------------------
I think if we do this (which we should) the work should also go into separating out the meta data storage and consensus service (async watchers and leader election). Once that is plug-able then you can use Exhibitor, Akka, Consul, Zookeeper, etc, whatever folks like to-do. From there I think the project can either adopt support for the exhibitor version or stick to the zkclient for out of the box support. Zkclient has worked and we should just abstract around it to reduce the most risk in code changes. Once its plug-able then Exhibitor can get used then too by folks that want to build and support it.
> 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)