On 5/20/10 12:04 PM, Lei Zhang wrote:
Seems you are passing in wrong arguments:
Should have been:
public ZooKeeper(String connectString, int sessionTimeout, Watcher
watcher)
throws IOException
What you have in your client code is:
On Thu, May 20, 2010 at 5:21 AM, Gregory
I feel like I'm missing something fairly fundamental here. I'm
building a clustered application that uses ZooKeeper (3.3.1) to store
its configuration information. There are 33 nodes in the cluster
(Amazon EC2 instance, if that matters), and I'm currently using a
single ZooKeeper instance. When
Hi Stephen, my comments inline below:
On 05/21/2010 09:31 AM, Stephen Green wrote:
I feel like I'm missing something fairly fundamental here. I'm
building a clustered application that uses ZooKeeper (3.3.1) to store
its configuration information. There are 33 nodes in the cluster
(Amazon EC2
On Fri, May 21, 2010 at 2:15 PM, Patrick Hunt ph...@apache.org wrote:
Hi Stephen, my comments inline below:
Thanks for the speedy response!
My understanding (having had a quick look at the code) is that the
client connection will send a ping every sessionTimeout * 2/3 ms or so
to keep the
On 05/21/2010 11:32 AM, Stephen Green wrote:
Right. The system can be very memory-intensive, but at the time these
are occurring, it's not under a really heavy load, and there's plenty
of heap available. However, while looking at a thread dump from one of
the nodes, I realized that a very poor
You may actually be swapping. That can be even worse than GC!
On Fri, May 21, 2010 at 11:32 AM, Stephen Green eelstretch...@gmail.comwrote:
Right. The system can be very memory-intensive, but at the time these
are occurring, it's not under a really heavy load, and there's plenty
of heap
