[
https://issues.apache.org/jira/browse/IGNITE-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698020#comment-14698020
]
Raúl Kripalani edited comment on IGNITE-1203 at 8/15/15 1:08 AM:
-----------------------------------------------------------------
My name is Raúl, not Paul ;-)
The use case is to provide another option to our users to discover nodes
dynamically via a mechanism that does not require nodes to be co-located (VM IP
Finder), a database (JDBC IP Finder, also a SPF by the way!), a network with
multicast permitted (I'd be shocked to find one out there) (Multicast IP
Finder) nor a shared filesystem (Shared FS IP Finder, also a SPF by the way!).
Those are the mechanisms currently offered by Ignite (without counting the
cloud-based ones) and I consider them to be insufficient.
I won't argue in depth about the virtues or limitations of Apache ZooKeeper –
this is not the right forum to do so. It is a widely adopted technology –
either directly or indirectly – and it only brings value to the Apache Ignite
project to support it. I see no downside. In fact, the more options we support
the better: ZeroMQ, etcd, Kubernetes Services (if running in that context),
etc.
What's the problem with providing more options to the users, if someone from
the community is willing to contribute them?
was (Author: raulvk):
My name is Raúl, not Paul ;-)
The use case is to provide another option to our users to discover nodes
dynamically via a mechanism that does not require nodes to be co-located (VM IP
Finder), a database (JDBC IP Finder, also a SPF by the way!), a network with
multicast permitted (I'd be shocked to find one out there) (Multicast IP
Finder) nor a shared filesystem (Shared FS IP Finder, also a SPF by the way!).
Those are the mechanisms currently offered by Ignite (without counting the
cloud-based ones) and i consider them to be insufficient.
I won't argue in depth about the virtues or limitations of Apache ZooKeeper –
this is not the right forum to do so. It is a widely adopted technology –
either directly or indirectly – and it only brings value to the Apache Ignite
project to support it. I see no downside. In fact, the more options we support
the better: ZeroMQ, etcd, Kubernetes Services (if running in that context),
etc.
What's the problem with providing more options to the users, if someone from
the community is willing to contribute them?
> Cluster Discovery via ZooKeeper
> -------------------------------
>
> Key: IGNITE-1203
> URL: https://issues.apache.org/jira/browse/IGNITE-1203
> Project: Ignite
> Issue Type: New Feature
> Components: general
> Reporter: Raúl Kripalani
> Assignee: Dmitriy Setrakyan
> Labels: discovery
>
> From their site:
> bq. ZooKeeper is a centralised service for maintaining configuration
> information, naming, providing distributed synchronisation, and providing
> group services.
> It is used by Kafka, Hadoop Yarn, HBase and many other technologies as a
> distributed service registry and discovery directory.
> It would be nice to support cluster discovery via ZK.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
