Re: DiscoverySpi based on Apache ZooKeeper

2018-03-07 Thread Sergey Chugunov
Hello Ken, Indeed tickets and documentation are confusing so let me clarify what they are about. Documentation at [1] and ticket IGNITE-1203 [2] are related to *TcpDiscoverySpi* component (see javadoc for in at [3]). More precisely they are about Zookeeper-based implementation of subcomponent cal

Re: DiscoverySpi based on Apache ZooKeeper

2018-03-07 Thread kcheng.mvp
There is a section in the document https://apacheignite.readme.io/docs/cluster-config#zookeeper-based-discovery. but I found below two tickets. https://issues.apache.org/jira/browse/IGNITE-1203 https://issues.apache.org/jira/browse/IGNITE-7222 I am a bit confused about which version supports t

Re: DiscoverySpi based on Apache ZooKeeper

2018-01-10 Thread Andrey Kornev
018 11:38 PM To: dev@ignite.apache.org Cc: Semyon Boikov Subject: Re: DiscoverySpi based on Apache ZooKeeper Hi Andrey, Could you please share detail of this API mismatch? AFAIK, the main guarantee we need for disco SPI is total message ordering. Zookeeper provides this guarantee. Moreover, Zookeeper is prov

Re: DiscoverySpi based on Apache ZooKeeper

2018-01-10 Thread Semyon Boikov
#x27;t be used to implement the cluster >> membership tracking in general. The problem is rather with DiscoverySpi >> semantics that require a different set of APIs than what Zookeeper provides. >> >> Regards >> Andrey >> >> __

Re: DiscoverySpi based on Apache ZooKeeper

2018-01-09 Thread Semyon Boikov
n Tue, Jan 9, 2018 at 3:39 AM, Semyon Boikov wrote: > > > Hi all, > > > > Currently I'm working on implementation of DiscoverySpi based on Apache > > ZooKeeper (ZookeeperDiscoverySpi) and want to share results of this work. > > > > In very large

Re: DiscoverySpi based on Apache ZooKeeper

2018-01-09 Thread Vladimir Ozerov
ary 9, 2018 3:39 AM > To: dev@ignite.apache.org > Subject: DiscoverySpi based on Apache ZooKeeper > > Hi all, > > Currently I'm working on implementation of DiscoverySpi based on Apache > ZooKeeper (ZookeeperDiscoverySpi) and want to share results of this work. >

Re: DiscoverySpi based on Apache ZooKeeper

2018-01-09 Thread Dmitriy Setrakyan
Thanks Semyon! I have a naming nitpick. Can we rename Problem to Failure, e.g. CommunicationProblemResolver to CommunicationFailureResolver? D. On Tue, Jan 9, 2018 at 3:39 AM, Semyon Boikov wrote: > Hi all, > > Currently I'm working on implementation of DiscoverySpi b

Re: DiscoverySpi based on Apache ZooKeeper

2018-01-09 Thread Andrey Kornev
Regards Andrey From: Semyon Boikov Sent: Tuesday, January 9, 2018 3:39 AM To: dev@ignite.apache.org Subject: DiscoverySpi based on Apache ZooKeeper Hi all, Currently I'm working on implementation of DiscoverySpi based on Apache ZooKeeper (ZookeeperDiscoverySp

DiscoverySpi based on Apache ZooKeeper

2018-01-09 Thread Semyon Boikov
Hi all, Currently I'm working on implementation of DiscoverySpi based on Apache ZooKeeper (ZookeeperDiscoverySpi) and want to share results of this work. In very large clusters (>1000 nodes) current default implementation of DiscoverySpi - TcpDiscoverySpi - has some significant d

[jira] [Created] (IGNITE-7222) DiscoverySpi based on Apache ZooKeeper

2017-12-17 Thread Semen Boikov (JIRA)
Semen Boikov created IGNITE-7222: Summary: DiscoverySpi based on Apache ZooKeeper Key: IGNITE-7222 URL: https://issues.apache.org/jira/browse/IGNITE-7222 Project: Ignite Issue Type: Task