x27;ll probably have to fix zkclient when we
upgrade in the near future.
.. Adam
On Wed, Jul 14, 2010 at 12:49 AM, Thomas Koch wrote:
> Jun Rao:
>> Hi,
>>
>> ZkClient (http://github.com/sgroschupf/zkclient) provides a nice wrapper
>> around the ZooKeeper client and han
Jun Rao:
> Hi,
>
> ZkClient (http://github.com/sgroschupf/zkclient) provides a nice wrapper
> around the ZooKeeper client and handles things like retry during
> ConnectionLoss events, and auto reconnect. Does anyone (other than Katta)
> use it? Would people recommend using it? T
bs up.
.. Adam
On Mon, Jul 12, 2010 at 4:10 PM, Jun Rao wrote:
> Hi,
>
> ZkClient (http://github.com/sgroschupf/zkclient) provides a nice wrapper
> around the ZooKeeper client and handles things like retry during
> ConnectionLoss events, and auto reconnect. Does anyone (other than
Hi,
ZkClient (http://github.com/sgroschupf/zkclient) provides a nice wrapper
around the ZooKeeper client and handles things like retry during
ConnectionLoss events, and auto reconnect. Does anyone (other than Katta)
use it? Would people recommend using it? Thanks,
Jun
assumptions/design of it. It could very well be useful for others. Its
just
that folks havent had much time to focus on these areas as yet.
Thanks
mahadev
On 5/4/10 2:58 PM, "Adam Rosien" wrote:
I use zkclient in my work at kaChing and I have mixed feelings about
it. On one hand
ll be useful for others. Its
just
that folks havent had much time to focus on these areas as yet.
Thanks
mahadev
On 5/4/10 2:58 PM, "Adam Rosien" wrote:
I use zkclient in my work at kaChing and I have mixed feelings about
it. On one hand it makes "easy things easy"
t; > Regarding re registration of watches, you can deifnitely write code and
>> > submit is as a part of well documented contrib module which lays out the
>> > assumptions/design of it. It could very well be useful for others. Its
>> just
>> > that folks havent had
t; just
> > that folks havent had much time to focus on these areas as yet.
> >
> > Thanks
> > mahadev
> >
> >
> > On 5/4/10 2:58 PM, "Adam Rosien" wrote:
> >
> >> I use zkclient in my work at kaChing and I have mixed feelings about
> >&g
documented contrib module which lays out the
> > assumptions/design of it. It could very well be useful for others. Its
> just
> > that folks havent had much time to focus on these areas as yet.
> >
> > Thanks
> > mahadev
> >
> >
> > On 5/4/10 2:58
>
> Thanks
> mahadev
>
>
> On 5/4/10 2:58 PM, "Adam Rosien" wrote:
>
>> I use zkclient in my work at kaChing and I have mixed feelings about
>> it. On one hand it makes "easy things easy" which is great, but on the
>> other hand I very fe
I don't think that zk is hard to get right.
What is hard is to layer a very different model on top of ZK that changes
the semantics significantly and that that translation right.
One of the very cool things about ZK is how easy it is to write correct
code. I know that Ben and co put a lot of tho
rt of well documented contrib module which lays out the
> assumptions/design of it. It could very well be useful for others. Its just
> that folks havent had much time to focus on these areas as yet.
>
> Thanks
> mahadev
>
>
> On 5/4/10 2:58 PM, "Adam Rosien" wrot
part of well documented contrib module which lays out the
assumptions/design of it. It could very well be useful for others. Its just
that folks havent had much time to focus on these areas as yet.
Thanks
mahadev
On 5/4/10 2:58 PM, "Adam Rosien" wrote:
> I use zkclient in my wor
I use zkclient in my work at kaChing and I have mixed feelings about
it. On one hand it makes "easy things easy" which is great, but on the
other hand I very few ideas what assumptions it makes "under the
hood". I also dislike some of the design choices such as unchecked
ex
In general, writing this sort of layer on top of ZK is very, very hard to
get really right for general use. In a simple use-case, you can probably
nail it but distributed systems are a Zoo, to coin a phrase. The problem is
that you are fundamentally changing the metaphors in use so assumptions ca
Katta generally has pretty decent code, though.
On Tue, May 4, 2010 at 12:39 PM, Jonathan Holloway<
jonathan.hollo...@gmail.com> wrote:
I came across this project on Github
http://github.com/sgroschupf/zkclient
for working with the Zookeeper API. Has anybody used it in the past?
rom
> katta. Katta generally has pretty decent code, though.
>
> On Tue, May 4, 2010 at 12:39 PM, Jonathan Holloway <
> jonathan.hollo...@gmail.com> wrote:
>
> > I came across this project on Github
> >
> > http://github.com/sgroschupf/zkclient
> >
hough.
On Tue, May 4, 2010 at 12:39 PM, Jonathan Holloway <
jonathan.hollo...@gmail.com> wrote:
> I came across this project on Github
>
> http://github.com/sgroschupf/zkclient
>
> for working with the Zookeeper API. Has anybody used it in the past? Is
> it
> a be
I came across this project on Github
http://github.com/sgroschupf/zkclient
for working with the Zookeeper API. Has anybody used it in the past? Is it
a better way of interacting with
a Zookeeper cluster?
Many thanks,
Jon.
Hi Patrick,
thanks - we will do, also thanks for all the feedback.
Stefan
On Oct 5, 2009, at 11:22 AM, Patrick Hunt wrote:
You might want to add a link to zkclient on this page:
http://wiki.apache.org/hadoop/ZooKeeper/UsefulTools
Patrick
Patrick Hunt wrote:
Ted Dunning wrote:
Judging by
You might want to add a link to zkclient on this page:
http://wiki.apache.org/hadoop/ZooKeeper/UsefulTools
Patrick
Patrick Hunt wrote:
Ted Dunning wrote:
Judging by history and that fact that only 40/127 issues are resolved,
3.3
is probably 3-6 months away. Is that a fair assessment?
Yes
Ted Dunning wrote:
Judging by history and that fact that only 40/127 issues are resolved, 3.3
is probably 3-6 months away. Is that a fair assessment?
Yes, that's fair.
Patrick
On Thu, Oct 1, 2009 at 11:13 AM, Patrick Hunt wrote:
One nice thing about ephemeral is that the Stat contains th
That looks really lovely.
Judging by history and that fact that only 40/127 issues are resolved, 3.3
is probably 3-6 months away. Is that a fair assessment?
On Thu, Oct 1, 2009 at 11:13 AM, Patrick Hunt wrote:
> One nice thing about ephemeral is that the Stat contains the owner
> sessionid. As
Ted Dunning wrote:
You may be able to tell if the file is yours be examining the content and
ownership, but this is pretty implementation dependent. In particular, it
makes queues very difficult to implement correctly. If this happens during
the creation of an ephemeral file, the only option ma
Not to harp on this ;-) but this sounds like something that would be a
very helpful addition to the README.
Ted Dunning wrote:
I think that another way to say this is that zkClient is going a bit for the
Spring philosophy that if the caller can't (or won't) be handling the
situation,
Peter Voss wrote:
On 01.10.2009, at 08:57, Patrick Hunt wrote:
2) what purpose does ZkEventThread serve?
ZkClient updates it's connection state from the ZooKeeper events. Based
on these it notifies listeners, updates it's connection state or
reconnects to ZooKeeper. ZkClient h
There is not much way to totally avoid this without massive performance loss
because the connection loss could be during the the time that the
confirmation is returning.
You may be able to tell if the file is yours be examining the content and
ownership, but this is pretty implementation dependent
I think that another way to say this is that zkClient is going a bit for the
Spring philosophy that if the caller can't (or won't) be handling the
situation, then they shouldn't be forced to declare it. The Spring
jdbcTemplate is a grand example of the benefits of this.
First imp
m
really expecting some helpful docs to get me bootstrapped.
2) what purpose does ZkEventThread serve?
ZkClient updates it's connection state from the ZooKeeper events.
Based on these it notifies listeners, updates it's connection state or
reconnects to ZooKeeper. ZkClient has its
no way to know which.
Mahadev is working on ZOOKEEPER-22 which will address this issue, but
that's a future version, not today.
4) when I saw that you had separated zkclient and zkconnection I thought
"ah, this is interesting" however when I saw the implementation I was
confused:
t's up to you to include
user, but apache discourages use of user for development discussion
(plus you'll pickup more developer insight there)
Patrick
Stefan Groschupf wrote:
Hi Zookeeper developer,
it would be great if you guys could give us some feedback about our
project zkclient.
per developer,
> it would be great if you guys could give us some feedback about our project
> zkclient.
> http://github.com/joa23/zkclient
> The main idea is making the life of lazy developers that only want minimal
> zk functionality much easier.
>
> We have a functionality
Hi Zookeeper developer,
it would be great if you guys could give us some feedback about our
project zkclient.
http://github.com/joa23/zkclient
The main idea is making the life of lazy developers that only want
minimal zk functionality much easier.
We have a functionality like zkclient mock
THat would be a great way to get really good feedback.
On Thu, Aug 13, 2009 at 4:13 PM, Stefan Groschupf wrote:
> If we have something clean and stable running we might contribute it back
> to the apache zk project.
--
Ted Dunning, CTO
DeepDyve
Hi All,
we recently spend some more quality time developing zkclient and since
there is more and more interest we started a mailing list.
You can subscribe to it here:
http://tech.groups.yahoo.com/group/zkclient-user/
The project can be find here:
http://github.com/joa23/zkclient/
The idea
35 matches
Mail list logo
