Hi,
I was wondering if there were plans to create a set of standard
ZooKeeper primitives, sort of like commons-collections. I figure it
would be mostly based off of the recipes on the ZK wiki, but it would
provide users with a slightly easier starting point, not to mention it
would be well-tested
Once that gets fixed we have a lock recipe, keptset
>> recipe, and there is a file monitoring library that is ready to go in.
>>
>> the key to ZOOKEEPER-80 is to fix the structure and the build process. if
>> you have a flash inspiration on how to best implement ZOOKEEPER-
I've come across the situation where a ZK instance will have an
expired connection and therefore all operations fail. Now AFAIK the
only way to recover is to create a new ZK instance with the old
session ID, correct?
Now, my problem is, the ZK instance may be shared -- not between
threads -- but
> mahadev
>
>
> On 2/12/09 10:58 AM, "Tom Nichols" wrote:
>
>> I've come across the situation where a ZK instance will have an
>> expired connection and therefore all operations fail. Now AFAIK the
>> only way to recover is to create a new ZK instan
gt;
> Mahadev Konar wrote:
>>
>> Hi Tom,
>> The session expired event means that the the server expired the client
>> and
>> that means the watches and ephemrals will go away for that node.
>>
>> How are you running your zookeeper quorum? Session expiry ev
e threadGroup.
Thanks again guys.
-Tom
> since session expiration really is a rare catastrophic event. (or at least it
> should be.) it is probably easiest to deal with it by starting with a fresh
> instance if your session expires.
>
> ben
> ____
&
g more about your env, OS & java version in particular, would also help
> us help you narrow things down. :-)
>
> Patrick
>
> Tom Nichols wrote:
>>
>> On Thu, Feb 12, 2009 at 4:11 PM, Benjamin Reed wrote:
>>>
>>> idleness is not a problem. the
