zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Camille Fournier <cami...@apache.org>
Subject Re: Basic client question
Date Mon, 24 Mar 2014 16:59:54 GMT
There is a connect timeout set automatically in the client based on the
session timeout divided by the number of servers in the cluster. You will
see a SessionTimeout exception if you exceed this connect timeout without
successfully connecting to one of the servers.
I would recommend using a higher-level client than the one that ships with
ZooKeeper, or else you have to build all of this in.
Even if you want to build your own, it would probably be useful reading the
documentation for something like Curator, which explains the choices that
client made to do this:

On Mon, Mar 24, 2014 at 12:48 PM, Dan Hopkins <danhopkins@victorops.com>wrote:

> Camille,
> I'm trying to figure out what timeout you're referring to? I'm using
> zkClient that ships with ZooKeeper and the only timeout I can see to
> configure is the "session timeout." Does this timeout work even if you
> never hear back from any server?
> Thanks,
> Dan
> On 03/24/2014 10:31 AM, Camille Fournier wrote:
>> So, client will never be able to reach the server again? The client that
>> you use (and we generally recommend you use an existing client library
>> like
>> Curator or even zkClient instead of writing your own) should have some
>> sort
>> of timeout configured so that if it gets disconnected and can't reach the
>> server within some period of time it gives up.
>> C
>> On Mon, Mar 24, 2014 at 12:01 PM, Dan Hopkins <danhopkins@victorops.com>
>> wrote:
>>  As a beginner using zookeeper I was wondering if anyone could help me
>>> understand how the java ZooKeeper client handles a permanent disconnect
>>> from the cluster. I'm curious because as I read the FAQ we can get a
>>> Session expiration if we ever connect to the server but I'm not sure what
>>> to do if I can never connect again.
>>> Is there a different exception thrown after a the client has detected
>>> permanent failure?
>>> I'm currently using Zk 3.3.4 in case the behavior has changed.
>>> Thanks for any pointers,
>>> Dan
>>> --
>>> Dan Hopkins | Programmer
>>> e: danhopkins@victorops.com
>>> Be Victorious
> --
> Dan Hopkins | Programmer
> e: danhopkins@victorops.com
> Be Victorious

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message