Hi all,
I had been working on zookeeper-22 and found out that it needs quite a few
extensive changes. We will need to do some memory measurements to see if it
has any memory impacts or not.
Since we are targetting 3.3 release for early march, ZOOKEEPER-22 would be
hard to get into 3.3. I am prop
I have found that ZK is an excellent diagnostic tool for misconfigured
systems. Every time I have seen excessive connection loss rates, it has not
been Zookeeper itself, but instead indicated problems on the client side.
On Tue, Feb 2, 2010 at 11:15 AM, Patrick Hunt wrote:
> For example "Hardwa
You should never see connection loss except in the case where you have
some network partition or some other issue that causes communication
issues btw the client and server. (client swapping? server swapping or
either having GC pause issues? etc...) Are you monitoring your
hosts/network/jvms, e
Ah ok, that makes a lot of sense. Thanks Ben!
On 02/01/2010 07:58 PM, Benjamin Reed wrote:
> sadly connectionloss is the really ugly part of zookeeper! it is a
> pain to deal with. i'm not sure we have best practice, but i can tell
> you what i do :) ZOOKEEPER-22 is meant to alleviate this proble
